Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f08d245e7469fefef8362798da5d24d7a2c22ee521a902931e832f0f84139d1

Tx prefix hash: 8fdaaba5502b22a3626708aea0e40fd9dc7e536b47897c01b353afd1f8c5578a
Tx public key: ee833f1f17ed95e6d8d33ab2b3bfdb1e3207ca51a5d28d32e731d8e869760e5f
Timestamp: 1726442528 Timestamp [UCT]: 2024-09-15 23:22:08 Age [y:d:h:m:s]: 00:073:15:29:51
Block: 1110964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52666 RingCT/type: yes/0
Extra: 01ee833f1f17ed95e6d8d33ab2b3bfdb1e3207ca51a5d28d32e731d8e869760e5f021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f1afbc8869c6a674b9a67326cb954860f7ce0668da39e1499d9e5a474c346a4 0.600000000000 1589757 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": 1110974, "vin": [ { "gen": { "height": 1110964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f1afbc8869c6a674b9a67326cb954860f7ce0668da39e1499d9e5a474c346a4" } } ], "extra": [ 1, 238, 131, 63, 31, 23, 237, 149, 230, 216, 211, 58, 178, 179, 191, 219, 30, 50, 7, 202, 81, 165, 210, 141, 50, 231, 49, 216, 232, 105, 118, 14, 95, 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