Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae8f3b93ec7daeaf266b1e41a65cd3a417a535a541ca9d3291b7714aafe85b97

Tx prefix hash: 7971fb30f85b2c3148a895309b16c3ca0dda370b850870bee1e76feef5fc93bd
Tx public key: c0fd2b097535496040710dbb2d4a5bb6744e1ab7f852afc320f93264ff107cbb
Timestamp: 1711730212 Timestamp [UCT]: 2024-03-29 16:36:52 Age [y:d:h:m:s]: 00:298:21:23:29
Block: 989011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213893 RingCT/type: yes/0
Extra: 01c0fd2b097535496040710dbb2d4a5bb6744e1ab7f852afc320f93264ff107cbb02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1697ebe3008a31e31423f5a877c8daaa4a766b9aa6ab541abf21d769552d1db6 0.600000000000 1449302 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": 989021, "vin": [ { "gen": { "height": 989011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1697ebe3008a31e31423f5a877c8daaa4a766b9aa6ab541abf21d769552d1db6" } } ], "extra": [ 1, 192, 253, 43, 9, 117, 53, 73, 96, 64, 113, 13, 187, 45, 74, 91, 182, 116, 78, 26, 183, 248, 82, 175, 195, 32, 249, 50, 100, 255, 16, 124, 187, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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