Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40f88044b14619e07e1d04e3a8f12563f7971ee8ea0da1e4a010e75babc0cb8c

Tx prefix hash: dcc1103729a20570bb341a3eccdc8302573bf665e38ef2d49ae8ad34e8dca985
Tx public key: c82b22ad5d469bb2ef332f91ea2fd9ba8748566cdd2357c293e8b8aaf03fbc65
Timestamp: 1743565609 Timestamp [UCT]: 2025-04-02 03:46:49 Age [y:d:h:m:s]: 00:300:18:30:58
Block: 1252423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212612 RingCT/type: yes/0
Extra: 01c82b22ad5d469bb2ef332f91ea2fd9ba8748566cdd2357c293e8b8aaf03fbc650211000000044060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ac61094964da9729d803c8c3f2e11293d6b2a4a64ba0f149dd316f256780c5f 0.600000000000 1739504 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": 1252433, "vin": [ { "gen": { "height": 1252423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ac61094964da9729d803c8c3f2e11293d6b2a4a64ba0f149dd316f256780c5f" } } ], "extra": [ 1, 200, 43, 34, 173, 93, 70, 155, 178, 239, 51, 47, 145, 234, 47, 217, 186, 135, 72, 86, 108, 221, 35, 87, 194, 147, 232, 184, 170, 240, 63, 188, 101, 2, 17, 0, 0, 0, 4, 64, 96, 246, 210, 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