Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 364fe84f5d67abac590a18a4f493d2982cc84f5810964d4a19dd7668b3e90234

Tx prefix hash: df44b77bbb399a760e814fcef79d5de489941c8297a590cb2fd6ed0449b8d8a1
Tx public key: ff57e7b1bd5e16f38c3668f15a5bedebddeccbae402b4ced7c786fbd44ffdf85
Timestamp: 1714340986 Timestamp [UCT]: 2024-04-28 21:49:46 Age [y:d:h:m:s]: 00:200:15:40:29
Block: 1010633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143635 RingCT/type: yes/0
Extra: 01ff57e7b1bd5e16f38c3668f15a5bedebddeccbae402b4ced7c786fbd44ffdf850211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7de7c252f627cc420bb6eaa2d094720854d754947e8e63394aec538e595e98a3 0.600000000000 1472643 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": 1010643, "vin": [ { "gen": { "height": 1010633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7de7c252f627cc420bb6eaa2d094720854d754947e8e63394aec538e595e98a3" } } ], "extra": [ 1, 255, 87, 231, 177, 189, 94, 22, 243, 140, 54, 104, 241, 90, 91, 237, 235, 221, 236, 203, 174, 64, 43, 76, 237, 124, 120, 111, 189, 68, 255, 223, 133, 2, 17, 0, 0, 0, 1, 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