Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab3a08d82f17f0c2973574b6593b89dd3c9ed2eaad5a8064c68b999f2d5a2d45

Tx prefix hash: 451f843ebe4ca1cb00de1794f795273522d196957f399fbd2ee8e5f60ae5f82f
Tx public key: 3c2408fc47cd17e3d34f7660e883248b4f4d32870678ccc360cf44d58b0c6f02
Timestamp: 1703425972 Timestamp [UCT]: 2023-12-24 13:52:52 Age [y:d:h:m:s]: 01:110:10:37:13
Block: 920151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340045 RingCT/type: yes/0
Extra: 013c2408fc47cd17e3d34f7660e883248b4f4d32870678ccc360cf44d58b0c6f0202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de63a58c4f907bce5ffc3b3485b346b3b8cfd06650e6932658410129e6ad2fa8 0.600000000000 1377829 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": 920161, "vin": [ { "gen": { "height": 920151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de63a58c4f907bce5ffc3b3485b346b3b8cfd06650e6932658410129e6ad2fa8" } } ], "extra": [ 1, 60, 36, 8, 252, 71, 205, 23, 227, 211, 79, 118, 96, 232, 131, 36, 139, 79, 77, 50, 135, 6, 120, 204, 195, 96, 207, 68, 213, 139, 12, 111, 2, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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