Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66c76659b98c1f1cecc77e9a3526e30fec38dd123509e8eeb0a8318d6d04657f

Tx prefix hash: 2c8b498ee5be8b90460ffa9b753b1e99d6065044e30c45cf66d493f9a233f467
Tx public key: e49006779e5e01d104b3a0d2c5f77c0074f83d13b41b4b7141df4791ad6fd3dc
Timestamp: 1632254511 Timestamp [UCT]: 2021-09-21 20:01:51 Age [y:d:h:m:s]: 03:224:05:53:35
Block: 338324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 936228 RingCT/type: yes/0
Extra: 01e49006779e5e01d104b3a0d2c5f77c0074f83d13b41b4b7141df4791ad6fd3dc0211000000153fc41461000000000000000000

1 output(s) for total of 46.450733642000 dcy

stealth address amount amount idx
00: 03fb29917987805d40aa86e7f5140e341be6d17d433a36e9646cae6df6f787d2 46.450733642000 696337 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": 338334, "vin": [ { "gen": { "height": 338324 } } ], "vout": [ { "amount": 46450733642, "target": { "key": "03fb29917987805d40aa86e7f5140e341be6d17d433a36e9646cae6df6f787d2" } } ], "extra": [ 1, 228, 144, 6, 119, 158, 94, 1, 209, 4, 179, 160, 210, 197, 247, 124, 0, 116, 248, 61, 19, 180, 27, 75, 113, 65, 223, 71, 145, 173, 111, 211, 220, 2, 17, 0, 0, 0, 21, 63, 196, 20, 97, 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