Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16c695d54fd19e0861edeea237bfa18287624f7926a36e7f7f1415a5b418c0ab

Tx prefix hash: ef837740a4ecfae406f7da981b759b77348a9714a24b220aac980c6f21549917
Tx public key: 0aca7304c0ad6eecd43ce4eeef91a372df7473e1e99a057c5bf2ec1e88f4fd98
Timestamp: 1720716453 Timestamp [UCT]: 2024-07-11 16:47:33 Age [y:d:h:m:s]: 00:302:21:13:06
Block: 1063501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216415 RingCT/type: yes/0
Extra: 010aca7304c0ad6eecd43ce4eeef91a372df7473e1e99a057c5bf2ec1e88f4fd9802110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c47466fa8f8403b604a03d6a07c74fb88d4c8f8886ee85daab661aac00fa9f9 0.600000000000 1534016 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": 1063511, "vin": [ { "gen": { "height": 1063501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c47466fa8f8403b604a03d6a07c74fb88d4c8f8886ee85daab661aac00fa9f9" } } ], "extra": [ 1, 10, 202, 115, 4, 192, 173, 110, 236, 212, 60, 228, 238, 239, 145, 163, 114, 223, 116, 115, 225, 233, 154, 5, 124, 91, 242, 236, 30, 136, 244, 253, 152, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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