Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02099362a3480d5a3d66415df7514c53914646591ce85a7d03d075a89f27478b

Tx prefix hash: 11817e2a66b22dd2518239205dae70cbb104f835da679c492715e9020da8aa0c
Tx public key: 37964ad885cb35c1fcda8dcb8c7d21e5d20e7c95748c7af19e232d357a4fd37e
Timestamp: 1718324383 Timestamp [UCT]: 2024-06-14 00:19:43 Age [y:d:h:m:s]: 00:167:23:51:23
Block: 1043670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120229 RingCT/type: yes/0
Extra: 0137964ad885cb35c1fcda8dcb8c7d21e5d20e7c95748c7af19e232d357a4fd37e02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 019e1d2d0356f29bfc8184fdfe583d1017ee2fcf3579b49df7dbac9a107d0983 0.600000000000 1512827 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": 1043680, "vin": [ { "gen": { "height": 1043670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "019e1d2d0356f29bfc8184fdfe583d1017ee2fcf3579b49df7dbac9a107d0983" } } ], "extra": [ 1, 55, 150, 74, 216, 133, 203, 53, 193, 252, 218, 141, 203, 140, 125, 33, 229, 210, 14, 124, 149, 116, 140, 122, 241, 158, 35, 45, 53, 122, 79, 211, 126, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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