Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bf789fbd73a5d1b1f5171d5083adbcab593270cfccb12ef3d967935b5b6c5af

Tx prefix hash: 588f8f0465063139eb503ac2ab1da2fed9f032a117799722aa3298a21f6b0a96
Tx public key: be1a1e9b052b94866c02e1358a359f691d13a36b2483c14fff5ddcfb96becc47
Timestamp: 1728448688 Timestamp [UCT]: 2024-10-09 04:38:08 Age [y:d:h:m:s]: 00:173:13:06:27
Block: 1127598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123816 RingCT/type: yes/0
Extra: 01be1a1e9b052b94866c02e1358a359f691d13a36b2483c14fff5ddcfb96becc4702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eb47336e97077a2aebfd9bcf075e419c05c32ffd8013cadc35e771df0a17049 0.600000000000 1610405 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": 1127608, "vin": [ { "gen": { "height": 1127598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eb47336e97077a2aebfd9bcf075e419c05c32ffd8013cadc35e771df0a17049" } } ], "extra": [ 1, 190, 26, 30, 155, 5, 43, 148, 134, 108, 2, 225, 53, 138, 53, 159, 105, 29, 19, 163, 107, 36, 131, 193, 79, 255, 93, 220, 251, 150, 190, 204, 71, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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