Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e5d408aca8d5ac4b0b009eb8a436d690ebd82e7f05debfa441bdcfb0eac4b0c

Tx prefix hash: 92924c8db391c39ebc72cfbd978e98b3b4fe7e81ff127c3c443014ba2f36e40a
Tx public key: 37db0c97f80463e4d893169feda0f78c4c84aeebb1eef728f26a2d6e03caeee6
Timestamp: 1733693144 Timestamp [UCT]: 2024-12-08 21:25:44 Age [y:d:h:m:s]: 00:103:01:18:23
Block: 1170990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73426 RingCT/type: yes/0
Extra: 0137db0c97f80463e4d893169feda0f78c4c84aeebb1eef728f26a2d6e03caeee6021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf8621aafb8e0185f838fca082a1f1eadf4a36d309bdc23b3832beec68787f41 0.600000000000 1656725 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": 1171000, "vin": [ { "gen": { "height": 1170990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf8621aafb8e0185f838fca082a1f1eadf4a36d309bdc23b3832beec68787f41" } } ], "extra": [ 1, 55, 219, 12, 151, 248, 4, 99, 228, 216, 147, 22, 159, 237, 160, 247, 140, 76, 132, 174, 235, 177, 238, 247, 40, 242, 106, 45, 110, 3, 202, 238, 230, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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