Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5076eaf8adcc96b11f48b5a7588ad95b23f2edb3fea51efa65f08e8acf71fc7e

Tx prefix hash: f577f2aa38cba8825207d93d89b32cd7b8ec916f06330d4037c82a9752b83c8d
Tx public key: fc61af1da3a07bf2470d45518827092921d9108c5426c78b768498983942f45c
Timestamp: 1581250002 Timestamp [UCT]: 2020-02-09 12:06:42 Age [y:d:h:m:s]: 05:088:00:40:32
Block: 61350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1215675 RingCT/type: yes/0
Extra: 01fc61af1da3a07bf2470d45518827092921d9108c5426c78b768498983942f45c02110000013356c366d3000000000000000000

1 output(s) for total of 384.353023339000 dcy

stealth address amount amount idx
00: 9fde3db899cdae92d518e2793aacfde7305c8cbfd036a2f6123ff1f7591bf9bd 384.353023339000 113048 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": 61360, "vin": [ { "gen": { "height": 61350 } } ], "vout": [ { "amount": 384353023339, "target": { "key": "9fde3db899cdae92d518e2793aacfde7305c8cbfd036a2f6123ff1f7591bf9bd" } } ], "extra": [ 1, 252, 97, 175, 29, 163, 160, 123, 242, 71, 13, 69, 81, 136, 39, 9, 41, 33, 217, 16, 140, 84, 38, 199, 139, 118, 132, 152, 152, 57, 66, 244, 92, 2, 17, 0, 0, 1, 51, 86, 195, 102, 211, 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