Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 020b74c541beacb02fa0c153687e6f276b06982e96ae32fcfee50824a5ae2d9e

Tx prefix hash: 1958d3a8d67d64d19086e3c4b2074bf810d509fbdec9d33ab444824060c65548
Tx public key: b58f1602041c9939b28c7c4d98abe8bf14c91c2f3e897d616f23647703e51b70
Timestamp: 1745577865 Timestamp [UCT]: 2025-04-25 10:44:25 Age [y:d:h:m:s]: 00:257:22:10:04
Block: 1269098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182127 RingCT/type: yes/0
Extra: 01b58f1602041c9939b28c7c4d98abe8bf14c91c2f3e897d616f23647703e51b700211000000076c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62eee9dad16e962f274209ba5dce4d94c93c27055e7c22d5320ad38791f658be 0.600000000000 1756333 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": 1269108, "vin": [ { "gen": { "height": 1269098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62eee9dad16e962f274209ba5dce4d94c93c27055e7c22d5320ad38791f658be" } } ], "extra": [ 1, 181, 143, 22, 2, 4, 28, 153, 57, 178, 140, 124, 77, 152, 171, 232, 191, 20, 201, 28, 47, 62, 137, 125, 97, 111, 35, 100, 119, 3, 229, 27, 112, 2, 17, 0, 0, 0, 7, 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