Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ec243d01adfb0d5eed543762e6ecbc30ef261752c21b416b28c4f900645f307

Tx prefix hash: f1b279b0ad4b7bf980d3858876e7b67f86fac4e6cca0f301b9e3715708fcca58
Tx public key: a6ef49efb44a2af1e29aa3d1f32c263cd96b51972bb4f559b77713cb4b66080c
Timestamp: 1582975450 Timestamp [UCT]: 2020-02-29 11:24:10 Age [y:d:h:m:s]: 05:005:14:22:17
Block: 73995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158357 RingCT/type: yes/0
Extra: 01a6ef49efb44a2af1e29aa3d1f32c263cd96b51972bb4f559b77713cb4b66080c02110000007a026b59f3000000000000000000

1 output(s) for total of 348.999373191000 dcy

stealth address amount amount idx
00: 16cd744ed2e57f1191b7efd85330f5471a107d74493ffc7972adab800cb1c697 348.999373191000 136756 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": 74005, "vin": [ { "gen": { "height": 73995 } } ], "vout": [ { "amount": 348999373191, "target": { "key": "16cd744ed2e57f1191b7efd85330f5471a107d74493ffc7972adab800cb1c697" } } ], "extra": [ 1, 166, 239, 73, 239, 180, 74, 42, 241, 226, 154, 163, 209, 243, 44, 38, 60, 217, 107, 81, 151, 43, 180, 245, 89, 183, 119, 19, 203, 75, 102, 8, 12, 2, 17, 0, 0, 0, 122, 2, 107, 89, 243, 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