Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6f9a3407d026b7b3e09ca619ccaaa3e48207e48f92ae6c0c3c78378035bf201

Tx prefix hash: 0c73b61c7cf2bfbcd8fafe4bf4eb6cb8b33bf6e69cc19e4b5478e91bf5c2b07d
Tx public key: 2b4a273baf2ee441ac8e8b46850094f89fc2749618d602cbbe3db428d4a5adfc
Timestamp: 1715368372 Timestamp [UCT]: 2024-05-10 19:12:52 Age [y:d:h:m:s]: 00:293:20:38:27
Block: 1019177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210004 RingCT/type: yes/0
Extra: 012b4a273baf2ee441ac8e8b46850094f89fc2749618d602cbbe3db428d4a5adfc02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffae53a45cc2cf03804de1b93d94c1954abdd024db80e86afdf815968f207633 0.600000000000 1483074 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": 1019187, "vin": [ { "gen": { "height": 1019177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffae53a45cc2cf03804de1b93d94c1954abdd024db80e86afdf815968f207633" } } ], "extra": [ 1, 43, 74, 39, 59, 175, 46, 228, 65, 172, 142, 139, 70, 133, 0, 148, 248, 159, 194, 116, 150, 24, 214, 2, 203, 190, 61, 180, 40, 212, 165, 173, 252, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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