Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d005cc1d5340f6a66993fee911f246fa03d2fa37102910cf08f4f1c275f3e4e

Tx prefix hash: 0cf86250c969d227661ce515ff8c4b24e3f428c1ea434184e1a01c94783adce7
Tx public key: 033e1cc9862155b9f25a2bf70561cdf860cfb0356e6049f3734202c87fb0eb4e
Timestamp: 1580885977 Timestamp [UCT]: 2020-02-05 06:59:37 Age [y:d:h:m:s]: 04:328:16:12:36
Block: 58856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126472 RingCT/type: yes/0
Extra: 01033e1cc9862155b9f25a2bf70561cdf860cfb0356e6049f3734202c87fb0eb4e021100000001bd0f9f9f000000000000000000

1 output(s) for total of 391.729663707000 dcy

stealth address amount amount idx
00: 8c2305a70063b91dec58e1cbfbf513eb83af23c5faf19909e323319bd2703c62 391.729663707000 108778 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": 58866, "vin": [ { "gen": { "height": 58856 } } ], "vout": [ { "amount": 391729663707, "target": { "key": "8c2305a70063b91dec58e1cbfbf513eb83af23c5faf19909e323319bd2703c62" } } ], "extra": [ 1, 3, 62, 28, 201, 134, 33, 85, 185, 242, 90, 43, 247, 5, 97, 205, 248, 96, 207, 176, 53, 110, 96, 73, 243, 115, 66, 2, 200, 127, 176, 235, 78, 2, 17, 0, 0, 0, 1, 189, 15, 159, 159, 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