Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bb997eb44b50b8a8c2cc1ac44f4fe9a2b27d09a7ff3634d7c4799bb47e79793

Tx prefix hash: 1c9ab0ac5b3de8026f43afdc975eb4cbd2be7e387d5ae54515cb94dcfeb1f0c5
Tx public key: 00a280ff476a6b8cfa25bea79fc795cffe31f46a41228559db02618babe06eb5
Timestamp: 1722964946 Timestamp [UCT]: 2024-08-06 17:22:26 Age [y:d:h:m:s]: 01:118:15:56:14
Block: 1082132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343320 RingCT/type: yes/0
Extra: 0100a280ff476a6b8cfa25bea79fc795cffe31f46a41228559db02618babe06eb5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df6a650ae3f40f55fbc35a8f2a57563170f6b4ee7f2aacee120fa7c784e952eb 0.600000000000 1555955 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": 1082142, "vin": [ { "gen": { "height": 1082132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df6a650ae3f40f55fbc35a8f2a57563170f6b4ee7f2aacee120fa7c784e952eb" } } ], "extra": [ 1, 0, 162, 128, 255, 71, 106, 107, 140, 250, 37, 190, 167, 159, 199, 149, 207, 254, 49, 244, 106, 65, 34, 133, 89, 219, 2, 97, 139, 171, 224, 110, 181, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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