Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f447cd97417c23fde763de966477e1f5e326851f05d0411fa2a0769e3fe54f6

Tx prefix hash: 310ddd32e519c72f8a192c16de4e677a1852b6bdd4c4a65cadf6b05468d3679f
Tx public key: 7a41b9bf8f1a84f8b835b83cb2cc233bc7b45f552dfbe52cbdbae65ad72a5454
Timestamp: 1626599383 Timestamp [UCT]: 2021-07-18 09:09:43 Age [y:d:h:m:s]: 03:170:16:13:55
Block: 296149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 893542 RingCT/type: yes/0
Extra: 017a41b9bf8f1a84f8b835b83cb2cc233bc7b45f552dfbe52cbdbae65ad72a5454021100000024ed79a617000000000000000000

1 output(s) for total of 64.081979964000 dcy

stealth address amount amount idx
00: 281fb4f0d16c167a0f07eb604d969f86606c1fb9641b5d3a4b46c2968b4f3f36 64.081979964000 620017 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": 296159, "vin": [ { "gen": { "height": 296149 } } ], "vout": [ { "amount": 64081979964, "target": { "key": "281fb4f0d16c167a0f07eb604d969f86606c1fb9641b5d3a4b46c2968b4f3f36" } } ], "extra": [ 1, 122, 65, 185, 191, 143, 26, 132, 248, 184, 53, 184, 60, 178, 204, 35, 59, 199, 180, 95, 85, 45, 251, 229, 44, 189, 186, 230, 90, 215, 42, 84, 84, 2, 17, 0, 0, 0, 36, 237, 121, 166, 23, 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