Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 797fe3e97c379896e2b12646101bf55b5dddef01119eba41d08f2e098665b306

Tx prefix hash: cd016374172dd903a18632056c4d6c164a79d7aa2535cb3c3e8ec935a32c910d
Tx public key: 7c4cd97b9fa75e502fba3c4c6b2e96f5c7644cbaa029b9ab5b56602ec91f85f8
Timestamp: 1726514945 Timestamp [UCT]: 2024-09-16 19:29:05 Age [y:d:h:m:s]: 00:248:05:10:11
Block: 1111569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177264 RingCT/type: yes/0
Extra: 017c4cd97b9fa75e502fba3c4c6b2e96f5c7644cbaa029b9ab5b56602ec91f85f802110000000291e13c04000000000000000000

1 output(s) for total of 0.608010000000 dcy

stealth address amount amount idx
00: e1d99c54ffbe8f0d76e9d5dbbd778b3025e2dac9481cb4b914c39c6bf383e045 0.608010000000 1590574 of 0

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": 1111579, "vin": [ { "gen": { "height": 1111569 } } ], "vout": [ { "amount": 608010000, "target": { "key": "e1d99c54ffbe8f0d76e9d5dbbd778b3025e2dac9481cb4b914c39c6bf383e045" } } ], "extra": [ 1, 124, 76, 217, 123, 159, 167, 94, 80, 47, 186, 60, 76, 107, 46, 150, 245, 199, 100, 76, 186, 160, 41, 185, 171, 91, 86, 96, 46, 201, 31, 133, 248, 2, 17, 0, 0, 0, 2, 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