Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f8eaa651dcca2a64806b9b5d73f563d3de5d0be137ae219dddfd44406e8e6bcd

Tx prefix hash: 3b549d248868d4aaa09e3dc6982b5b21827f41dbbb5d4ccc3e5b497175015d8b
Tx public key: 0a25bed5f1641301f1ef6a3ee09b4922bceffbff04a484f11a13d83de9496920
Timestamp: 1717393069 Timestamp [UCT]: 2024-06-03 05:37:49 Age [y:d:h:m:s]: 01:170:12:07:37
Block: 1035957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380433 RingCT/type: yes/0
Extra: 010a25bed5f1641301f1ef6a3ee09b4922bceffbff04a484f11a13d83de94969200211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c928c3dc9f0ac2cb0b0b76ab708936180f8807414371a63ea3e994f5fde8ee4 0.600000000000 1504482 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1035967, "vin": [ { "gen": { "height": 1035957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c928c3dc9f0ac2cb0b0b76ab708936180f8807414371a63ea3e994f5fde8ee4" } } ], "extra": [ 1, 10, 37, 190, 213, 241, 100, 19, 1, 241, 239, 106, 62, 224, 155, 73, 34, 188, 239, 251, 255, 4, 164, 132, 241, 26, 19, 216, 61, 233, 73, 105, 32, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8