Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b20e2b8cb1b54d8612723ed3a202ba56dafb8afc7a70eb1b085e0b09070b3ddf

Tx prefix hash: f3ff29ffac27f1af9edb513d014e80d663483508416e42824a98696479fd656d
Tx public key: 900646519fb46f5e7be357059b926f550ed3ff1d07ea2c4779b4c851a34630e2
Timestamp: 1681437303 Timestamp [UCT]: 2023-04-14 01:55:03 Age [y:d:h:m:s]: 01:263:06:12:10
Block: 738090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449647 RingCT/type: yes/0
Extra: 01900646519fb46f5e7be357059b926f550ed3ff1d07ea2c4779b4c851a34630e2021100000004b3164c24000000000000000000

1 output(s) for total of 2.199893492000 dcy

stealth address amount amount idx
00: c170e60269662f39832ea6ffb3d8b45af11c6e275665709f81235babce613400 2.199893492000 1184733 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": 738100, "vin": [ { "gen": { "height": 738090 } } ], "vout": [ { "amount": 2199893492, "target": { "key": "c170e60269662f39832ea6ffb3d8b45af11c6e275665709f81235babce613400" } } ], "extra": [ 1, 144, 6, 70, 81, 159, 180, 111, 94, 123, 227, 87, 5, 155, 146, 111, 85, 14, 211, 255, 29, 7, 234, 44, 71, 121, 180, 200, 81, 163, 70, 48, 226, 2, 17, 0, 0, 0, 4, 179, 22, 76, 36, 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