Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a669a8fdd76a513e7d29634d0d3b6c5aab1b16a56e4e48c982fe1a1d0c6391e

Tx prefix hash: 619818442165b19c17b508e51d39246c355013fee75bda8ecb84259c776978ae
Tx public key: c021d9cadfc2ef4bbe678ea11ac2000ff67f2321deb27c6444bc5d648518a6a9
Timestamp: 1580975172 Timestamp [UCT]: 2020-02-06 07:46:12 Age [y:d:h:m:s]: 04:284:19:02:56
Block: 59552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1095131 RingCT/type: yes/0
Extra: 01c021d9cadfc2ef4bbe678ea11ac2000ff67f2321deb27c6444bc5d648518a6a902110000000403d36d11000000000000000000

1 output(s) for total of 389.655061331000 dcy

stealth address amount amount idx
00: 1d8cb64b5e4806344b30b89d0609f59a914c42e1018c8756906f1015b2b31ab8 389.655061331000 109974 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": 59562, "vin": [ { "gen": { "height": 59552 } } ], "vout": [ { "amount": 389655061331, "target": { "key": "1d8cb64b5e4806344b30b89d0609f59a914c42e1018c8756906f1015b2b31ab8" } } ], "extra": [ 1, 192, 33, 217, 202, 223, 194, 239, 75, 190, 103, 142, 161, 26, 194, 0, 15, 246, 127, 35, 33, 222, 178, 124, 100, 68, 188, 93, 100, 133, 24, 166, 169, 2, 17, 0, 0, 0, 4, 3, 211, 109, 17, 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