Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c85769a09c76fe325a5c751931fd2f7de1dac6011acc25363f52164558d1225e

Tx prefix hash: 81c34f500cf3a6c0c0f2e559a421a76ef27f8baab5f4b559d3d7c759d61251c1
Tx public key: 87d4f0c86c5dbf6250db04263b2cdcd5e97633786de04e8308f8f893fdd3a910
Timestamp: 1686302834 Timestamp [UCT]: 2023-06-09 09:27:14 Age [y:d:h:m:s]: 01:350:04:11:14
Block: 778446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511486 RingCT/type: yes/0
Extra: 0187d4f0c86c5dbf6250db04263b2cdcd5e97633786de04e8308f8f893fdd3a910021100000001faf35c9c000000000000000000

1 output(s) for total of 1.616908392000 dcy

stealth address amount amount idx
00: d54f5492d89a18a5fc063fefddaa7b65d23e7fe44a60ce10fdcb2d34b7adffcf 1.616908392000 1228071 of 0

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": 778456, "vin": [ { "gen": { "height": 778446 } } ], "vout": [ { "amount": 1616908392, "target": { "key": "d54f5492d89a18a5fc063fefddaa7b65d23e7fe44a60ce10fdcb2d34b7adffcf" } } ], "extra": [ 1, 135, 212, 240, 200, 108, 93, 191, 98, 80, 219, 4, 38, 59, 44, 220, 213, 233, 118, 51, 120, 109, 224, 78, 131, 8, 248, 248, 147, 253, 211, 169, 16, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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