Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9e6e9e90141ad8764215d695dbf70ad58b9ddb1d74159f35304b6ceb6c79320

Tx prefix hash: 7ee7f3acee9dcf09b593ae8a56ebe4d5b7301d09ac2b35b2208e429b4a59d5b1
Tx public key: bff304d13918543e7fd219112a27998264c1f3c033a2c049a21e06bd284191ce
Timestamp: 1727086743 Timestamp [UCT]: 2024-09-23 10:19:03 Age [y:d:h:m:s]: 00:151:20:32:46
Block: 1116307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108303 RingCT/type: yes/0
Extra: 01bff304d13918543e7fd219112a27998264c1f3c033a2c049a21e06bd284191ce021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64a5450fb6f0166825ce6d946c1979c12b9016b3894cb70f2af1768e461f802f 0.600000000000 1596742 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": 1116317, "vin": [ { "gen": { "height": 1116307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64a5450fb6f0166825ce6d946c1979c12b9016b3894cb70f2af1768e461f802f" } } ], "extra": [ 1, 191, 243, 4, 209, 57, 24, 84, 62, 127, 210, 25, 17, 42, 39, 153, 130, 100, 193, 243, 192, 51, 162, 192, 73, 162, 30, 6, 189, 40, 65, 145, 206, 2, 17, 0, 0, 0, 8, 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