Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73419f859485cc1acd188be756ff5bfb36caa8a29770abcda6446410a64d9b7e

Tx prefix hash: 1d99c4e17b8f36e5afb7fe2c3065afcb08e649d65274a47583262b654ca5d0d8
Tx public key: e0c9bd1a2d5cdfee0e6d1911e9d10132f083b986a3ea860dc11b7ce61d528c18
Timestamp: 1726427248 Timestamp [UCT]: 2024-09-15 19:07:28 Age [y:d:h:m:s]: 00:076:14:15:29
Block: 1110840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54772 RingCT/type: yes/0
Extra: 01e0c9bd1a2d5cdfee0e6d1911e9d10132f083b986a3ea860dc11b7ce61d528c18021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e48ee94c7a089a3d22bb26d0319276810f309a88c087a4fbca71150e6127d778 0.600000000000 1589593 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": 1110850, "vin": [ { "gen": { "height": 1110840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e48ee94c7a089a3d22bb26d0319276810f309a88c087a4fbca71150e6127d778" } } ], "extra": [ 1, 224, 201, 189, 26, 45, 92, 223, 238, 14, 109, 25, 17, 233, 209, 1, 50, 240, 131, 185, 134, 163, 234, 134, 13, 193, 27, 124, 230, 29, 82, 140, 24, 2, 17, 0, 0, 0, 3, 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