Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cce56a48f3dec4c5db53c6384c0f191b21070a08d5430ab8128ce4b2fc4f362

Tx prefix hash: fc849e99b300fe2f1fd8f2f487a31aa2949144d065c3d1a1292970d22ddacba1
Tx public key: e2e985155e638c5afffb15f0eb80e94943962517dc4ea5b2ddcee3da9c4f2213
Timestamp: 1745768907 Timestamp [UCT]: 2025-04-27 15:48:27 Age [y:d:h:m:s]: 00:206:16:13:02
Block: 1270685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145422 RingCT/type: yes/0
Extra: 01e2e985155e638c5afffb15f0eb80e94943962517dc4ea5b2ddcee3da9c4f221302110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5984d75cd8468deee5bd0b1154a619ecab269711e8c37c27cc108963dcc3fa07 0.600000000000 1757930 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": 1270695, "vin": [ { "gen": { "height": 1270685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5984d75cd8468deee5bd0b1154a619ecab269711e8c37c27cc108963dcc3fa07" } } ], "extra": [ 1, 226, 233, 133, 21, 94, 99, 140, 90, 255, 251, 21, 240, 235, 128, 233, 73, 67, 150, 37, 23, 220, 78, 165, 178, 221, 206, 227, 218, 156, 79, 34, 19, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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