Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61c71edd01c82f33a72c7bdd518ac147fd246ce635fbc53e3592f6f37017cf39

Tx prefix hash: c282b2a93a497fa6b0838a32c23f222c70fab61619ef1830e9d47ef253deea55
Tx public key: 717e34a6d34dad58e1f8edf9b53e72c1e3f9c01475a9d14d18fffa2413bcedf9
Timestamp: 1752774524 Timestamp [UCT]: 2025-07-17 17:48:44 Age [y:d:h:m:s]: 00:197:09:19:59
Block: 1327559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139773 RingCT/type: yes/0
Extra: 01717e34a6d34dad58e1f8edf9b53e72c1e3f9c01475a9d14d18fffa2413bcedf90211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 808936b599b720ac108656a421bedb09ca154f9368b083eafd772dee1b69903a 0.600000000000 1815316 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": 1327569, "vin": [ { "gen": { "height": 1327559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "808936b599b720ac108656a421bedb09ca154f9368b083eafd772dee1b69903a" } } ], "extra": [ 1, 113, 126, 52, 166, 211, 77, 173, 88, 225, 248, 237, 249, 181, 62, 114, 193, 227, 249, 192, 20, 117, 169, 209, 77, 24, 255, 250, 36, 19, 188, 237, 249, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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