Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d944ef6b3411888cb0389fbbb52ea56f1cfb5f92dda203fe2c693759597dc9b

Tx prefix hash: e59db7294bffcaaa2383365b1fb117723df057e594f9e82b3de624803f9a176c
Tx public key: 7f15d6b5d779ae5e39761b2f09c1af96ebe583c41921cdda0b1330751f2c2672
Timestamp: 1707421949 Timestamp [UCT]: 2024-02-08 19:52:29 Age [y:d:h:m:s]: 01:055:06:05:14
Block: 953266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300534 RingCT/type: yes/0
Extra: 017f15d6b5d779ae5e39761b2f09c1af96ebe583c41921cdda0b1330751f2c26720211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3172fd79cd700a59aad30e84e703de779f7b2f517941d4afe940857b5a50573 0.600000000000 1412456 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": 953276, "vin": [ { "gen": { "height": 953266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3172fd79cd700a59aad30e84e703de779f7b2f517941d4afe940857b5a50573" } } ], "extra": [ 1, 127, 21, 214, 181, 215, 121, 174, 94, 57, 118, 27, 47, 9, 193, 175, 150, 235, 229, 131, 196, 25, 33, 205, 218, 11, 19, 48, 117, 31, 44, 38, 114, 2, 17, 0, 0, 0, 4, 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