Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b50a3d9120e84957de2539720d18e161433955ca68389b07bb288b8694f55823

Tx prefix hash: d7ce46bb6433edf6abcfdf9d9ac41dbd70b8f504233e5ea53e4ccf89eb613351
Tx public key: 5656aeb6ea2f49ff2c7e9a6692d9d87dac5fd0dc7b8cd203d1e0726dc3ff6c42
Timestamp: 1577666723 Timestamp [UCT]: 2019-12-30 00:45:23 Age [y:d:h:m:s]: 05:306:00:02:33
Block: 34661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1366205 RingCT/type: yes/0
Extra: 015656aeb6ea2f49ff2c7e9a6692d9d87dac5fd0dc7b8cd203d1e0726dc3ff6c4202110000001ffeadaf7f000000000000000000

1 output(s) for total of 471.144986372000 dcy

stealth address amount amount idx
00: b64c0b4fa3a10d4277bd2dc922d194e45f80cf1598deed75da64b7ecc77060ae 471.144986372000 58369 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": 34671, "vin": [ { "gen": { "height": 34661 } } ], "vout": [ { "amount": 471144986372, "target": { "key": "b64c0b4fa3a10d4277bd2dc922d194e45f80cf1598deed75da64b7ecc77060ae" } } ], "extra": [ 1, 86, 86, 174, 182, 234, 47, 73, 255, 44, 126, 154, 102, 146, 217, 216, 125, 172, 95, 208, 220, 123, 140, 210, 3, 209, 224, 114, 109, 195, 255, 108, 66, 2, 17, 0, 0, 0, 31, 254, 173, 175, 127, 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