Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66ffdbdd26ac2d2eed27c88a325737214515a76ceb0ecabca81547cb15600e2d

Tx prefix hash: 87e03203dc0375f0348570eb8cc6f995fb30d54d5359cb874d5232a15a8bb8a9
Tx public key: 93299c5a64a71424c96c22710e925046cf379535c3b5fcadd05fa8179780d1c3
Timestamp: 1723354888 Timestamp [UCT]: 2024-08-11 05:41:28 Age [y:d:h:m:s]: 00:256:00:35:24
Block: 1085367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182881 RingCT/type: yes/0
Extra: 0193299c5a64a71424c96c22710e925046cf379535c3b5fcadd05fa8179780d1c3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 868c7e2af2e8da18ddbac1009fcb6d8d6f00c41cf1c1ef867f0d3d1e0b2f76a8 0.600000000000 1559936 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": 1085377, "vin": [ { "gen": { "height": 1085367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "868c7e2af2e8da18ddbac1009fcb6d8d6f00c41cf1c1ef867f0d3d1e0b2f76a8" } } ], "extra": [ 1, 147, 41, 156, 90, 100, 167, 20, 36, 201, 108, 34, 113, 14, 146, 80, 70, 207, 55, 149, 53, 195, 181, 252, 173, 208, 95, 168, 23, 151, 128, 209, 195, 2, 17, 0, 0, 0, 1, 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