Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 863bc4d00a2945c590afa21522e5028cc3b9b5f29e7980ca1c8ffd6080adac4b

Tx prefix hash: 4cd8555334967ca6f62011b8c9e3060d8e61b90e2b1665db96cdb0fd2136ffed
Tx public key: 62bba970742a4dd9a2c77ae5019bf7d1ae01cedb1348432b4e054010c283b1a1
Timestamp: 1732477151 Timestamp [UCT]: 2024-11-24 19:39:11 Age [y:d:h:m:s]: 00:198:09:55:41
Block: 1160901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141645 RingCT/type: yes/0
Extra: 0162bba970742a4dd9a2c77ae5019bf7d1ae01cedb1348432b4e054010c283b1a10211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 882c05637a8fe524e5b332d8130b9872d6a3eba223b009494bff839d6d1ad8fd 0.600000000000 1646552 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": 1160911, "vin": [ { "gen": { "height": 1160901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "882c05637a8fe524e5b332d8130b9872d6a3eba223b009494bff839d6d1ad8fd" } } ], "extra": [ 1, 98, 187, 169, 112, 116, 42, 77, 217, 162, 199, 122, 229, 1, 155, 247, 209, 174, 1, 206, 219, 19, 72, 67, 43, 78, 5, 64, 16, 194, 131, 177, 161, 2, 17, 0, 0, 0, 1, 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