Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 997f464a89051ea6482febb35d36cda49ff7b2ef298918372736d09f980780a6

Tx prefix hash: ffe140c4a1ca223f9b2dfae0d46eb5e679d021130b3f380ae37e96d6e1fb3bcf
Tx public key: e9b85fdb10b0b20c9c85f3c2f0ce6b9ab4de09d38cc8694e906b9e714fb9f1e0
Timestamp: 1712675524 Timestamp [UCT]: 2024-04-09 15:12:04 Age [y:d:h:m:s]: 00:237:02:38:11
Block: 996808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169766 RingCT/type: yes/0
Extra: 01e9b85fdb10b0b20c9c85f3c2f0ce6b9ab4de09d38cc8694e906b9e714fb9f1e002110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bdbed71750067bd260c0a4d5d6b1cea6756fa803aed3cd8ff4ccb04275ba840 0.600000000000 1457236 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": 996818, "vin": [ { "gen": { "height": 996808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bdbed71750067bd260c0a4d5d6b1cea6756fa803aed3cd8ff4ccb04275ba840" } } ], "extra": [ 1, 233, 184, 95, 219, 16, 176, 178, 12, 156, 133, 243, 194, 240, 206, 107, 154, 180, 222, 9, 211, 140, 200, 105, 78, 144, 107, 158, 113, 79, 185, 241, 224, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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