Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24f30ee6981200980d3fb852735ddb65fd451da33a9e897ec1903e92053e0cb5

Tx prefix hash: bb4bc07307d702474f635bb2205a0d7da24bad8eeae3e1bfdedb940dc7184dae
Tx public key: 21e6f9ca1697d974d57ef93e0c6f1509070a2bf98fec31a49a1447a6b9a873a4
Timestamp: 1723143739 Timestamp [UCT]: 2024-08-08 19:02:19 Age [y:d:h:m:s]: 00:265:10:32:24
Block: 1083613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189604 RingCT/type: yes/0
Extra: 0121e6f9ca1697d974d57ef93e0c6f1509070a2bf98fec31a49a1447a6b9a873a402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0aa9e97505703299973f00925eaec947dbadf115c20b6f69dd85050fba2f01a 0.600000000000 1557598 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": 1083623, "vin": [ { "gen": { "height": 1083613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0aa9e97505703299973f00925eaec947dbadf115c20b6f69dd85050fba2f01a" } } ], "extra": [ 1, 33, 230, 249, 202, 22, 151, 217, 116, 213, 126, 249, 62, 12, 111, 21, 9, 7, 10, 43, 249, 143, 236, 49, 164, 154, 20, 71, 166, 185, 168, 115, 164, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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