Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1066fa992392f168c2c0c81d275eb44eab903c32003b4010c7b79c379fd026eb

Tx prefix hash: a233bac13efd784a6fd24b6fc3b1403f6a01cf6ac69b7eeb7f097caa872e68a5
Tx public key: 7a9e934ece0ab799dd20671088e5fe70af77bcd3551f0df92d31505ca2a2f258
Timestamp: 1716886902 Timestamp [UCT]: 2024-05-28 09:01:42 Age [y:d:h:m:s]: 00:290:00:59:35
Block: 1031759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207291 RingCT/type: yes/0
Extra: 017a9e934ece0ab799dd20671088e5fe70af77bcd3551f0df92d31505ca2a2f2580211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80ade9827d9b5e91e59230f93cd2b614bf7aee72dbbb70fb6b546ccc67542b75 0.600000000000 1500208 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": 1031769, "vin": [ { "gen": { "height": 1031759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80ade9827d9b5e91e59230f93cd2b614bf7aee72dbbb70fb6b546ccc67542b75" } } ], "extra": [ 1, 122, 158, 147, 78, 206, 10, 183, 153, 221, 32, 103, 16, 136, 229, 254, 112, 175, 119, 188, 211, 85, 31, 13, 249, 45, 49, 80, 92, 162, 162, 242, 88, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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