Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c65cc3ce58a6fd762faa7a8c70325d122eaa5b1906c73bb6eeef43993fc756d6

Tx prefix hash: 56bf7cd5374f9ecceb530f831f5e4a79d2ecb0ead5924af9d4673079bdf49b8a
Tx public key: 658dc6f0a553207d1ca67b8e3b4f83f306c8d1f28640ed897c519603de885857
Timestamp: 1754631213 Timestamp [UCT]: 2025-08-08 05:33:33 Age [y:d:h:m:s]: 00:013:12:59:48
Block: 1342608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8840 RingCT/type: yes/0
Extra: 01658dc6f0a553207d1ca67b8e3b4f83f306c8d1f28640ed897c519603de88585702110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a88bfd89de0343321eb03a7a0bf4b269b8138727bfc0845d3146b656e1fb18c 0.600000000000 1830441 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": 1342618, "vin": [ { "gen": { "height": 1342608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a88bfd89de0343321eb03a7a0bf4b269b8138727bfc0845d3146b656e1fb18c" } } ], "extra": [ 1, 101, 141, 198, 240, 165, 83, 32, 125, 28, 166, 123, 142, 59, 79, 131, 243, 6, 200, 209, 242, 134, 64, 237, 137, 124, 81, 150, 3, 222, 136, 88, 87, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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