Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff58b50bd85bf6700c5e6154ba029f2b81e6f7a2a372156021f681fcca1dde9f

Tx prefix hash: a0de6546aadece862f31a2b915b66f846e3509c9133e191ea6ba1f37af0433ec
Tx public key: 400429f17d10fdfba9ddfb108372b8c3974dd717de5045d421a7a38bb45b990c
Timestamp: 1733012757 Timestamp [UCT]: 2024-12-01 00:25:57 Age [y:d:h:m:s]: 00:129:19:59:32
Block: 1165340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92586 RingCT/type: yes/0
Extra: 01400429f17d10fdfba9ddfb108372b8c3974dd717de5045d421a7a38bb45b990c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 453b95f4651273a79289d92f3d8e35e8cb0d33364c446295d6ccb2eb9b0ab22d 0.600000000000 1651015 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": 1165350, "vin": [ { "gen": { "height": 1165340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "453b95f4651273a79289d92f3d8e35e8cb0d33364c446295d6ccb2eb9b0ab22d" } } ], "extra": [ 1, 64, 4, 41, 241, 125, 16, 253, 251, 169, 221, 251, 16, 131, 114, 184, 195, 151, 77, 215, 23, 222, 80, 69, 212, 33, 167, 163, 139, 180, 91, 153, 12, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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