Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8ecbb3bcb7c13efb4903a6a07fbec9bdee8fb1f313f920c4e2c1bd02e9a2aef

Tx prefix hash: 50b3909323f46db1b665ee12c458c2fd9138f03d2442c252fec9c333131dc0d4
Tx public key: a5199ad1aad2fa1a633d637f873174c17e5c83929af8eb0e5ec1444a31e6cd1d
Timestamp: 1581901927 Timestamp [UCT]: 2020-02-17 01:12:07 Age [y:d:h:m:s]: 05:069:04:06:03
Block: 66347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1202592 RingCT/type: yes/0
Extra: 01a5199ad1aad2fa1a633d637f873174c17e5c83929af8eb0e5ec1444a31e6cd1d0211000000068a2ee0d9000000000000000000

1 output(s) for total of 369.969272922000 dcy

stealth address amount amount idx
00: 97fe32a4bfd0593d4a1f396e3642f77c24d0f9e895d3616b63267a7ffb436787 369.969272922000 122258 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": 66357, "vin": [ { "gen": { "height": 66347 } } ], "vout": [ { "amount": 369969272922, "target": { "key": "97fe32a4bfd0593d4a1f396e3642f77c24d0f9e895d3616b63267a7ffb436787" } } ], "extra": [ 1, 165, 25, 154, 209, 170, 210, 250, 26, 99, 61, 99, 127, 135, 49, 116, 193, 126, 92, 131, 146, 154, 248, 235, 14, 94, 193, 68, 74, 49, 230, 205, 29, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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