Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5692c086a9e933ad70447b9cc3fc5008f0608602165b94ab75280441c66e3102

Tx prefix hash: bf71289d49df310d3cc4e69a97c073c2fa97f16618db48849a7896dd0fd5d1d0
Tx public key: 6b9d7ba4e3f72b7950357f0edb097e7df718093ac6e033c4117827802f331cdc
Timestamp: 1763267275 Timestamp [UCT]: 2025-11-16 04:27:55 Age [y:d:h:m:s]: 00:012:02:55:19
Block: 1413139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8675 RingCT/type: yes/0
Extra: 016b9d7ba4e3f72b7950357f0edb097e7df718093ac6e033c4117827802f331cdc021100000009da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bb4002b487a7c21eea8207b4eb5dae9a9251886ed634c519cb6c0bce2bd3378 0.600000000000 1901616 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": 1413149, "vin": [ { "gen": { "height": 1413139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bb4002b487a7c21eea8207b4eb5dae9a9251886ed634c519cb6c0bce2bd3378" } } ], "extra": [ 1, 107, 157, 123, 164, 227, 247, 43, 121, 80, 53, 127, 14, 219, 9, 126, 125, 247, 24, 9, 58, 198, 224, 51, 196, 17, 120, 39, 128, 47, 51, 28, 220, 2, 17, 0, 0, 0, 9, 218, 85, 72, 72, 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