Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16663fdf1072523b21d404610bd59e1e21a7db8b5253975b976e2449f16d5533

Tx prefix hash: c9651ed693301be0dbc6e1cd4fb0f461feed7b831567ce74af433211de30c80e
Tx public key: 89d4577e0f41c4dfe2b65077082983d075bb2821087c9c0c16cf02338d3288e9
Timestamp: 1726012510 Timestamp [UCT]: 2024-09-10 23:55:10 Age [y:d:h:m:s]: 00:208:13:49:56
Block: 1107403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148888 RingCT/type: yes/0
Extra: 0189d4577e0f41c4dfe2b65077082983d075bb2821087c9c0c16cf02338d3288e9021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a34d129abf2a286f9d9b31ad9e01d6fd8531a224fd2f7e31526510d84a43fb6 0.600000000000 1585014 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": 1107413, "vin": [ { "gen": { "height": 1107403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a34d129abf2a286f9d9b31ad9e01d6fd8531a224fd2f7e31526510d84a43fb6" } } ], "extra": [ 1, 137, 212, 87, 126, 15, 65, 196, 223, 226, 182, 80, 119, 8, 41, 131, 208, 117, 187, 40, 33, 8, 124, 156, 12, 22, 207, 2, 51, 141, 50, 136, 233, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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