Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a4277c29f6dbe98b54573e16c78809575a246d8b186db317c5cb73f7772a491

Tx prefix hash: 4d7fc4c5fbdbff29360bb5a3acdf88eace0dd6894d9881d5fa408d7c193879af
Tx public key: ecebc76abde4bb1bf8c001e966d61623ed412ba2e3a46f60d95ead7c9bbc5ae7
Timestamp: 1752277551 Timestamp [UCT]: 2025-07-11 23:45:51 Age [y:d:h:m:s]: 00:178:00:10:12
Block: 1323535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126004 RingCT/type: yes/0
Extra: 01ecebc76abde4bb1bf8c001e966d61623ed412ba2e3a46f60d95ead7c9bbc5ae70211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e36f2bd77ea6aaba34069373a10287fd0068142e476536991b3a3f6cb6bd3d1c 0.600000000000 1811274 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": 1323545, "vin": [ { "gen": { "height": 1323535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e36f2bd77ea6aaba34069373a10287fd0068142e476536991b3a3f6cb6bd3d1c" } } ], "extra": [ 1, 236, 235, 199, 106, 189, 228, 187, 27, 248, 192, 1, 233, 102, 214, 22, 35, 237, 65, 43, 162, 227, 164, 111, 96, 217, 94, 173, 124, 155, 188, 90, 231, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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