Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1f03de3e13bceab11747daa47543a7c9f4c2a26c931b2cb9f1653d8503fc9b2

Tx prefix hash: b3886bb24192d88c610c591ab3c855bc19eb525f22756ac02aa94b653112afc0
Tx public key: 5d7fd9983e8cc7cd6fd32f1f8cf004669423f3c2918cdf70e52096dbeb3247f8
Timestamp: 1674903568 Timestamp [UCT]: 2023-01-28 10:59:28 Age [y:d:h:m:s]: 02:284:05:45:10
Block: 684556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 722503 RingCT/type: yes/0
Extra: 015d7fd9983e8cc7cd6fd32f1f8cf004669423f3c2918cdf70e52096dbeb3247f80211000000015029cbac000000000000000000

1 output(s) for total of 3.309647456000 dcy

stealth address amount amount idx
00: 7038948a444dd2d77fa021259a421fad8b536516234fa8975fce2eb317011b11 3.309647456000 1126807 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": 684566, "vin": [ { "gen": { "height": 684556 } } ], "vout": [ { "amount": 3309647456, "target": { "key": "7038948a444dd2d77fa021259a421fad8b536516234fa8975fce2eb317011b11" } } ], "extra": [ 1, 93, 127, 217, 152, 62, 140, 199, 205, 111, 211, 47, 31, 140, 240, 4, 102, 148, 35, 243, 194, 145, 140, 223, 112, 229, 32, 150, 219, 235, 50, 71, 248, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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