Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58b5a16d1c5332abde173765fd4e79cc2162ec21d0e95802492b9dc4add58fc9

Tx prefix hash: 1263fab428d18107bf45d66be5decc21602543b5c7a3b5758c51a8c40264da92
Tx public key: 3c7a2574cd99a4c937165066be7bb26b914bf3cad6ae175a72610ca303e8c4ca
Timestamp: 1760957873 Timestamp [UCT]: 2025-10-20 10:57:53 Age [y:d:h:m:s]: 00:019:00:24:31
Block: 1394019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13589 RingCT/type: yes/0
Extra: 013c7a2574cd99a4c937165066be7bb26b914bf3cad6ae175a72610ca303e8c4ca021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d19d7a38562d3f64bf457f1cf9e1d1c861df70c49c14c49a35dcbd1e536dde4a 0.600000000000 1882286 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": 1394029, "vin": [ { "gen": { "height": 1394019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d19d7a38562d3f64bf457f1cf9e1d1c861df70c49c14c49a35dcbd1e536dde4a" } } ], "extra": [ 1, 60, 122, 37, 116, 205, 153, 164, 201, 55, 22, 80, 102, 190, 123, 178, 107, 145, 75, 243, 202, 214, 174, 23, 90, 114, 97, 12, 163, 3, 232, 196, 202, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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