Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 536a1c08fb7546a0751e0a8fb3507477af2fa43df3a695e5e55f3574c509d923

Tx prefix hash: 305e114c76805e8fb767813d771ec69f1ff25e2933aa9632b58e27cba614803f
Tx public key: db88d3c5717dd4b871b0fbbc48bbce2fd555a85b008e0fdfaf906ee3cca660cb
Timestamp: 1763793215 Timestamp [UCT]: 2025-11-22 06:33:35 Age [y:d:h:m:s]: 00:005:13:45:42
Block: 1417487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4006 RingCT/type: yes/0
Extra: 01db88d3c5717dd4b871b0fbbc48bbce2fd555a85b008e0fdfaf906ee3cca660cb021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8136427867b4907d0305d98f21a321b8f59bea341d7d8b27dd80e3708dec1bbe 0.600000000000 1906010 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": 1417497, "vin": [ { "gen": { "height": 1417487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8136427867b4907d0305d98f21a321b8f59bea341d7d8b27dd80e3708dec1bbe" } } ], "extra": [ 1, 219, 136, 211, 197, 113, 125, 212, 184, 113, 176, 251, 188, 72, 187, 206, 47, 213, 85, 168, 91, 0, 142, 15, 223, 175, 144, 110, 227, 204, 166, 96, 203, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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