Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 603884f46b7b0a52069947a52dbc579b76d8b402f425fc6992567d5ecc78b4b3

Tx prefix hash: 0efb8d65cad463122d2c9097f14f1341d9bbb27972c380b6827ff84ad4df9738
Tx public key: e3288553b98d60e9ef441713897bce9c9ab526a2d913b626ed5d5395c12a0c3c
Timestamp: 1745767277 Timestamp [UCT]: 2025-04-27 15:21:17 Age [y:d:h:m:s]: 00:253:04:55:48
Block: 1270672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178754 RingCT/type: yes/0
Extra: 01e3288553b98d60e9ef441713897bce9c9ab526a2d913b626ed5d5395c12a0c3c0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20030ab2171d15023c6035cdaa47af9a1b43ac4d6bfa6ff58c3be4b632164ebb 0.600000000000 1757917 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": 1270682, "vin": [ { "gen": { "height": 1270672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20030ab2171d15023c6035cdaa47af9a1b43ac4d6bfa6ff58c3be4b632164ebb" } } ], "extra": [ 1, 227, 40, 133, 83, 185, 141, 96, 233, 239, 68, 23, 19, 137, 123, 206, 156, 154, 181, 38, 162, 217, 19, 182, 38, 237, 93, 83, 149, 193, 42, 12, 60, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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