Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62ef165408e59834a00aa2314d1b3d70d6563fbe21049da546d89fdc0f0f3786

Tx prefix hash: 4a86f3b7b2744ec2e6bd3ceb48e38062383a1d35d011b58fb1fed01502088d47
Tx public key: e4193016b48fe67e5e15eee3826e86740c444a7e8bb66d3d6ccb6749dc9d2412
Timestamp: 1703034623 Timestamp [UCT]: 2023-12-20 01:10:23 Age [y:d:h:m:s]: 01:182:07:38:28
Block: 916909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391333 RingCT/type: yes/0
Extra: 01e4193016b48fe67e5e15eee3826e86740c444a7e8bb66d3d6ccb6749dc9d2412021100000008e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15a998d60b1b029c63aae33c60632bab89b3bc1397c52efb044197e782fdf349 0.600000000000 1374471 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": 916919, "vin": [ { "gen": { "height": 916909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15a998d60b1b029c63aae33c60632bab89b3bc1397c52efb044197e782fdf349" } } ], "extra": [ 1, 228, 25, 48, 22, 180, 143, 230, 126, 94, 21, 238, 227, 130, 110, 134, 116, 12, 68, 74, 126, 139, 182, 109, 61, 108, 203, 103, 73, 220, 157, 36, 18, 2, 17, 0, 0, 0, 8, 228, 187, 107, 131, 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