Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fc9a7ed0cee42065cf3427428af28d5835340ae88ca720943ce0b537eab43a1

Tx prefix hash: c9ccacc8dcd2d866c6077d0682f5047a195ba62a020d049cf94cf2ca48d127ea
Tx public key: 34b52fe2bec506bf246ae13d9b09dc03cffee9066479ec261ea3e5e8bf72680d
Timestamp: 1755517512 Timestamp [UCT]: 2025-08-18 11:45:12 Age [y:d:h:m:s]: 00:094:02:37:11
Block: 1349167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67119 RingCT/type: yes/0
Extra: 0134b52fe2bec506bf246ae13d9b09dc03cffee9066479ec261ea3e5e8bf72680d021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8d80ad7b5e6399016c7fd330b533a0f7dc7d337d4cbcc6c25e05d35d26196cd 0.600000000000 1837098 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": 1349177, "vin": [ { "gen": { "height": 1349167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8d80ad7b5e6399016c7fd330b533a0f7dc7d337d4cbcc6c25e05d35d26196cd" } } ], "extra": [ 1, 52, 181, 47, 226, 190, 197, 6, 191, 36, 106, 225, 61, 155, 9, 220, 3, 207, 254, 233, 6, 100, 121, 236, 38, 30, 163, 229, 232, 191, 114, 104, 13, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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