Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32589b385d6ca240f0f0a98d8d85e75ec694c6ac1fd739bb78d0de442bfc1b7d

Tx prefix hash: f91c8d6aa43fcd1e10027683f3e17a70726fde256d3673c708faf5e87e8076eb
Tx public key: 6342cf55b44e3e7e1c48d7c124b513db32e490f59798b2ec2efb2c141fc2b876
Timestamp: 1702240646 Timestamp [UCT]: 2023-12-10 20:37:26 Age [y:d:h:m:s]: 01:339:08:18:15
Block: 910323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501394 RingCT/type: yes/0
Extra: 016342cf55b44e3e7e1c48d7c124b513db32e490f59798b2ec2efb2c141fc2b8760211000000024b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8feb35421ad4e24952c4031d17b81ca9633fa6258ead782214bb41032e9d04e 0.600000000000 1367472 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": 910333, "vin": [ { "gen": { "height": 910323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8feb35421ad4e24952c4031d17b81ca9633fa6258ead782214bb41032e9d04e" } } ], "extra": [ 1, 99, 66, 207, 85, 180, 78, 62, 126, 28, 72, 215, 193, 36, 181, 19, 219, 50, 228, 144, 245, 151, 152, 178, 236, 46, 251, 44, 20, 31, 194, 184, 118, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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