Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad0dc87f174b71cdf7c271a71056aa280dded87a3cd276083e31bb9a3e3d071d

Tx prefix hash: b66edd18b6aea68f13836b26b1106adac23eea707e3c2084b8a9e04be48825c5
Tx public key: a8a824742491af3ab228b81a55d43f8bdf7f1544825f974a049fb57ff2df6b3f
Timestamp: 1577724067 Timestamp [UCT]: 2019-12-30 16:41:07 Age [y:d:h:m:s]: 05:147:00:18:27
Block: 35165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1254872 RingCT/type: yes/0
Extra: 01a8a824742491af3ab228b81a55d43f8bdf7f1544825f974a049fb57ff2df6b3f0211000000094ac5aa02000000000000000000

1 output(s) for total of 469.336804431000 dcy

stealth address amount amount idx
00: 64dde8ae41e2af9806efe3acf334d04894e920e6039b29e8ce69d259f93c638d 469.336804431000 59237 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": 35175, "vin": [ { "gen": { "height": 35165 } } ], "vout": [ { "amount": 469336804431, "target": { "key": "64dde8ae41e2af9806efe3acf334d04894e920e6039b29e8ce69d259f93c638d" } } ], "extra": [ 1, 168, 168, 36, 116, 36, 145, 175, 58, 178, 40, 184, 26, 85, 212, 63, 139, 223, 127, 21, 68, 130, 95, 151, 74, 4, 159, 181, 127, 242, 223, 107, 63, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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