Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c921efcd879ec994d4e28d97eaece9f67bea2c6a134a187460bde2f8142ccdfa

Tx prefix hash: bfce1753377e288e2ff13b3a1c12c04585b575d000d900a25cf67d5a646a748a
Tx public key: c19d7270f07dfe46cf25d068af218ccebec54ee9086a51df0e46b35cb4012158
Timestamp: 1580623127 Timestamp [UCT]: 2020-02-02 05:58:47 Age [y:d:h:m:s]: 05:276:20:08:58
Block: 56965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1347505 RingCT/type: yes/0
Extra: 01c19d7270f07dfe46cf25d068af218ccebec54ee9086a51df0e46b35cb401215802110000000149b77a3d000000000000000000

1 output(s) for total of 397.422206721000 dcy

stealth address amount amount idx
00: 55afd3a378e8bdc31f7e49d1b3a140c0cc82c77932d5bbf1ce7a1f174912d145 397.422206721000 105028 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": 56975, "vin": [ { "gen": { "height": 56965 } } ], "vout": [ { "amount": 397422206721, "target": { "key": "55afd3a378e8bdc31f7e49d1b3a140c0cc82c77932d5bbf1ce7a1f174912d145" } } ], "extra": [ 1, 193, 157, 114, 112, 240, 125, 254, 70, 207, 37, 208, 104, 175, 33, 140, 206, 190, 197, 78, 233, 8, 106, 81, 223, 14, 70, 179, 92, 180, 1, 33, 88, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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