Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42b5447191d65d3b151e1da596a770aa8e0e93a2161044ea04d8feae7b449dbc

Tx prefix hash: 37351f442ee33a5d3de98d8507c915e84033409e97e6a676ab2fb2d17417cbd5
Tx public key: 17c70889620624298c284424f8c9a1294515741927d4ae3ef4d38b2d809abf6a
Timestamp: 1747653761 Timestamp [UCT]: 2025-05-19 11:22:41 Age [y:d:h:m:s]: 00:141:17:41:03
Block: 1286281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98937 RingCT/type: yes/0
Extra: 0117c70889620624298c284424f8c9a1294515741927d4ae3ef4d38b2d809abf6a02110000000d1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcc651e5db6f0e38ce2e63923c007b3d8c9fbb62e6391fe0a01367145206e24a 0.600000000000 1773746 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": 1286291, "vin": [ { "gen": { "height": 1286281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcc651e5db6f0e38ce2e63923c007b3d8c9fbb62e6391fe0a01367145206e24a" } } ], "extra": [ 1, 23, 199, 8, 137, 98, 6, 36, 41, 140, 40, 68, 36, 248, 201, 161, 41, 69, 21, 116, 25, 39, 212, 174, 62, 244, 211, 139, 45, 128, 154, 191, 106, 2, 17, 0, 0, 0, 13, 31, 144, 81, 122, 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