Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73496012c396b7ccc3bf8ae4b49c9fafbb5f8c9ed405e5f03e3ae4256d9922bd

Tx prefix hash: a9d36d08a5251a7453eb89a7c91a8cc0ca1b5e63077025bcf2c2004cdadb8e06
Tx public key: 959e1ccd1cd2dca8cbb1abe5339c566af18aadde30b9e69e555c6af393c19fb1
Timestamp: 1747359414 Timestamp [UCT]: 2025-05-16 01:36:54 Age [y:d:h:m:s]: 00:187:02:40:28
Block: 1283833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131442 RingCT/type: yes/0
Extra: 01959e1ccd1cd2dca8cbb1abe5339c566af18aadde30b9e69e555c6af393c19fb1021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13442b4615bc2823221fb5d66759eba0a391c9171f4ecb8ac628293e122c194a 0.600000000000 1771252 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": 1283843, "vin": [ { "gen": { "height": 1283833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13442b4615bc2823221fb5d66759eba0a391c9171f4ecb8ac628293e122c194a" } } ], "extra": [ 1, 149, 158, 28, 205, 28, 210, 220, 168, 203, 177, 171, 229, 51, 156, 86, 106, 241, 138, 173, 222, 48, 185, 230, 158, 85, 92, 106, 243, 147, 193, 159, 177, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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