Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3649b87cfd82d079859cfd1b7681e249822312ec49e4a25b17566473d722d4f7

Tx prefix hash: a052bc881a963be79a98eb2134c60287a8b62adfb33e0d6fcc1318475ce10cc5
Tx public key: 9690cee9e2494dc7edc12a80914ac1e731c674d18a04d8043f75f43ec984f432
Timestamp: 1743892308 Timestamp [UCT]: 2025-04-05 22:31:48 Age [y:d:h:m:s]: 00:227:00:42:49
Block: 1255133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159992 RingCT/type: yes/0
Extra: 019690cee9e2494dc7edc12a80914ac1e731c674d18a04d8043f75f43ec984f4320211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93965be94d2f47eec0fcad6719e8364038d7312e2b2dcad0bc78986638929c91 0.600000000000 1742236 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": 1255143, "vin": [ { "gen": { "height": 1255133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93965be94d2f47eec0fcad6719e8364038d7312e2b2dcad0bc78986638929c91" } } ], "extra": [ 1, 150, 144, 206, 233, 226, 73, 77, 199, 237, 193, 42, 128, 145, 74, 193, 231, 49, 198, 116, 209, 138, 4, 216, 4, 63, 117, 244, 62, 201, 132, 244, 50, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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