Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b17123a006c7ac3d95b2040b7b584196952a3c8284f6f7b3f61afe0793009d1e

Tx prefix hash: f8a312138b62d5ce643308a2fed0bb4a9825651d8677414f38397c6e2fcceda0
Tx public key: 8e9f7264a5ec90586e0dbf9508fd31519bc609637534e0af02f100f84978ac88
Timestamp: 1745423739 Timestamp [UCT]: 2025-04-23 15:55:39 Age [y:d:h:m:s]: 00:283:18:10:12
Block: 1267813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200442 RingCT/type: yes/0
Extra: 018e9f7264a5ec90586e0dbf9508fd31519bc609637534e0af02f100f84978ac880211000000076c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12d4c515ae548eb2af45a654d51f4aa1e4069b9d9d83f89013afc1b7b5fb0a10 0.600000000000 1755042 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": 1267823, "vin": [ { "gen": { "height": 1267813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12d4c515ae548eb2af45a654d51f4aa1e4069b9d9d83f89013afc1b7b5fb0a10" } } ], "extra": [ 1, 142, 159, 114, 100, 165, 236, 144, 88, 110, 13, 191, 149, 8, 253, 49, 81, 155, 198, 9, 99, 117, 52, 224, 175, 2, 241, 0, 248, 73, 120, 172, 136, 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