Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ac60800060a93abc34aa7ad0ae8d4eb3ee1bf6082b9e57f592bfb40c24145cc

Tx prefix hash: 834c3a752e258410fd9131e739217b38b6032a3b3659264a8c05aa33ef14e743
Tx public key: 6f74254aabcc55b9cfb26f4610412655d4d9010e66d5c7cf151de2b057e81db5
Timestamp: 1701741532 Timestamp [UCT]: 2023-12-05 01:58:52 Age [y:d:h:m:s]: 01:145:13:09:29
Block: 906176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365204 RingCT/type: yes/0
Extra: 016f74254aabcc55b9cfb26f4610412655d4d9010e66d5c7cf151de2b057e81db5021100000002faf35c9c000000000000000000

1 output(s) for total of 0.610186669000 dcy

stealth address amount amount idx
00: c5a9ff03443a1587d97efc1c10ca81e705963c356080b027f13e32612f69b599 0.610186669000 1363103 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": 906186, "vin": [ { "gen": { "height": 906176 } } ], "vout": [ { "amount": 610186669, "target": { "key": "c5a9ff03443a1587d97efc1c10ca81e705963c356080b027f13e32612f69b599" } } ], "extra": [ 1, 111, 116, 37, 74, 171, 204, 85, 185, 207, 178, 111, 70, 16, 65, 38, 85, 212, 217, 1, 14, 102, 213, 199, 207, 21, 29, 226, 176, 87, 232, 29, 181, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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