Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5f2e46212bf07b561e574e8f6885e26c851ca5683b8307e9f504aaca8682ac8

Tx prefix hash: 159f3efb5e31bc044a318bcc8860a3cb996e8255fb554d367fed04e8495ec6b5
Tx public key: 27e91c03d2f9a5b42d17f643bf2002d3d88f379b2b567a93458dcec93bc510f2
Timestamp: 1755220412 Timestamp [UCT]: 2025-08-15 01:13:32 Age [y:d:h:m:s]: 00:097:03:33:58
Block: 1346903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69108 RingCT/type: yes/0
Extra: 0127e91c03d2f9a5b42d17f643bf2002d3d88f379b2b567a93458dcec93bc510f202110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7549647dc3d97f26c1f8a84621240cba24ebee4d0b02f12dc39f35f857ddddd4 0.600000000000 1834812 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": 1346913, "vin": [ { "gen": { "height": 1346903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7549647dc3d97f26c1f8a84621240cba24ebee4d0b02f12dc39f35f857ddddd4" } } ], "extra": [ 1, 39, 233, 28, 3, 210, 249, 165, 180, 45, 23, 246, 67, 191, 32, 2, 211, 216, 143, 55, 155, 43, 86, 122, 147, 69, 141, 206, 201, 59, 197, 16, 242, 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