Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e8c9a51fe9de63775f0ca57dc6a40c228cc4ef789059a13338bdb85c53f5076

Tx prefix hash: ddbcd39e91ea3945192b44c7907264baa8c1e089159a536cfedb1058df693a76
Tx public key: 2084a38dfce3fb971a8a5ce70355c99a4407c76ccacd57fe7380cb930db7b5a9
Timestamp: 1740206583 Timestamp [UCT]: 2025-02-22 06:43:03 Age [y:d:h:m:s]: 00:228:20:54:13
Block: 1224605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161298 RingCT/type: yes/0
Extra: 012084a38dfce3fb971a8a5ce70355c99a4407c76ccacd57fe7380cb930db7b5a90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7b03d339cd0bf71769651588d3181595a6c92b4252d65508b6ff1e4fd64e3ea 0.600000000000 1711468 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": 1224615, "vin": [ { "gen": { "height": 1224605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7b03d339cd0bf71769651588d3181595a6c92b4252d65508b6ff1e4fd64e3ea" } } ], "extra": [ 1, 32, 132, 163, 141, 252, 227, 251, 151, 26, 138, 92, 231, 3, 85, 201, 154, 68, 7, 199, 108, 202, 205, 87, 254, 115, 128, 203, 147, 13, 183, 181, 169, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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