Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4c77000cbff8435189ec0c59ce3b7b6db677bceab93d0cb6cde6e3658319bb8

Tx prefix hash: d3e80e6acbb78aa2b381c34286e09bf05fe0eb44c0d3b34b0d312a2835f9e247
Tx public key: 655da0d7a309ccb81f59b930feb49a88ab03f2b28e4a5a1a6d127b59169ec3e6
Timestamp: 1638652680 Timestamp [UCT]: 2021-12-04 21:18:00 Age [y:d:h:m:s]: 02:346:06:07:04
Block: 388496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 765473 RingCT/type: yes/0
Extra: 01655da0d7a309ccb81f59b930feb49a88ab03f2b28e4a5a1a6d127b59169ec3e6021100000003a272b9cb000000000000000000

1 output(s) for total of 31.677569171000 dcy

stealth address amount amount idx
00: df5af368e102202853be1a12e92d8e5008aa6963baf8d78b01f839846fed31ab 31.677569171000 783165 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": 388506, "vin": [ { "gen": { "height": 388496 } } ], "vout": [ { "amount": 31677569171, "target": { "key": "df5af368e102202853be1a12e92d8e5008aa6963baf8d78b01f839846fed31ab" } } ], "extra": [ 1, 101, 93, 160, 215, 163, 9, 204, 184, 31, 89, 185, 48, 254, 180, 154, 136, 171, 3, 242, 178, 142, 74, 90, 26, 109, 18, 123, 89, 22, 158, 195, 230, 2, 17, 0, 0, 0, 3, 162, 114, 185, 203, 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