Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f865633f79422685126e2e1608697d737a6cde846e1fcc0eeae43e5c50cdac2

Tx prefix hash: bc19975b6d5ae5ca0224d7a37891cb77fc600b2470a7ac4532f8535635135b36
Tx public key: 6e7f1ed735e9b20b12108d91ddd8681875a9f4ae5f48477f19695e663f1a4cfe
Timestamp: 1703475843 Timestamp [UCT]: 2023-12-25 03:44:03 Age [y:d:h:m:s]: 02:036:11:00:46
Block: 920566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545680 RingCT/type: yes/0
Extra: 016e7f1ed735e9b20b12108d91ddd8681875a9f4ae5f48477f19695e663f1a4cfe0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b024a2f56766680b17ddd977c5c0594bc3881868d6a339e118b3013d0ebb852e 0.600000000000 1378246 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": 920576, "vin": [ { "gen": { "height": 920566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b024a2f56766680b17ddd977c5c0594bc3881868d6a339e118b3013d0ebb852e" } } ], "extra": [ 1, 110, 127, 30, 215, 53, 233, 178, 11, 18, 16, 141, 145, 221, 216, 104, 24, 117, 169, 244, 174, 95, 72, 71, 127, 25, 105, 94, 102, 63, 26, 76, 254, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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