Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c9392da5539981d53e4d4421d5614e0585c7c2bb1fe289a99d81fa7c873395c

Tx prefix hash: 640512a1c437c424c1810a202116b26727fdda80f7d8c27aa3c325558abac2dd
Tx public key: dc3e5aa4633f98ac86075074e1c18348f4a147ecdd74e33ff8f037a83bb588ae
Timestamp: 1745064220 Timestamp [UCT]: 2025-04-19 12:03:40 Age [y:d:h:m:s]: 00:206:01:26:06
Block: 1264836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144991 RingCT/type: yes/0
Extra: 01dc3e5aa4633f98ac86075074e1c18348f4a147ecdd74e33ff8f037a83bb588ae02110000000ddbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 314bdf05d8cf809a3cd7fed7859b3e9dd7d7f8d46f446354e01a74a007608e2a 0.600000000000 1752037 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": 1264846, "vin": [ { "gen": { "height": 1264836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "314bdf05d8cf809a3cd7fed7859b3e9dd7d7f8d46f446354e01a74a007608e2a" } } ], "extra": [ 1, 220, 62, 90, 164, 99, 63, 152, 172, 134, 7, 80, 116, 225, 193, 131, 72, 244, 161, 71, 236, 221, 116, 227, 63, 248, 240, 55, 168, 59, 181, 136, 174, 2, 17, 0, 0, 0, 13, 219, 181, 113, 193, 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