Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 608a0df75716da5e8b7ee6a23edb806307d2f345ce5ec817fa5d6c1255417258

Tx prefix hash: 9656534716b4e9f321711c6ab82fa0c411ab826d5b3b69557ac1d212be12958b
Tx public key: 54bae21c9b58e90e8750c3235b7d788b9966cae916bf87edc802bc51a2b01afb
Timestamp: 1634880266 Timestamp [UCT]: 2021-10-22 05:24:26 Age [y:d:h:m:s]: 03:068:05:00:14
Block: 357890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 827061 RingCT/type: yes/0
Extra: 0154bae21c9b58e90e8750c3235b7d788b9966cae916bf87edc802bc51a2b01afb02110000000b7e786c8c000000000000000000

1 output(s) for total of 40.009421768000 dcy

stealth address amount amount idx
00: ed68b22b745959d836142eafb790c83f940e7c26197168503f814487a2f36a01 40.009421768000 729543 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": 357900, "vin": [ { "gen": { "height": 357890 } } ], "vout": [ { "amount": 40009421768, "target": { "key": "ed68b22b745959d836142eafb790c83f940e7c26197168503f814487a2f36a01" } } ], "extra": [ 1, 84, 186, 226, 28, 155, 88, 233, 14, 135, 80, 195, 35, 91, 125, 120, 139, 153, 102, 202, 233, 22, 191, 135, 237, 200, 2, 188, 81, 162, 176, 26, 251, 2, 17, 0, 0, 0, 11, 126, 120, 108, 140, 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