Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6607668830b7ed5b39228f1106468967ac8704a1fff34dde7edf68d9a6aea4a9

Tx prefix hash: d45a76131f3e11fdf18a9d17b2a9141f5e8673e4d41b7269e719abc304baa7ca
Tx public key: 1c7e4b6cb95a13f4c9f60df4755f54ea54b3026ab8785088ff28b0beaff08733
Timestamp: 1581821201 Timestamp [UCT]: 2020-02-16 02:46:41 Age [y:d:h:m:s]: 04:327:20:00:26
Block: 65747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126723 RingCT/type: yes/0
Extra: 011c7e4b6cb95a13f4c9f60df4755f54ea54b3026ab8785088ff28b0beaff087330211000000094943cd9f000000000000000000

1 output(s) for total of 371.666746571000 dcy

stealth address amount amount idx
00: bbfaaceb6ff48dd15a651099a60a559aeae97c050bfb3339b94fdfd9dc36c672 371.666746571000 121326 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": 65757, "vin": [ { "gen": { "height": 65747 } } ], "vout": [ { "amount": 371666746571, "target": { "key": "bbfaaceb6ff48dd15a651099a60a559aeae97c050bfb3339b94fdfd9dc36c672" } } ], "extra": [ 1, 28, 126, 75, 108, 185, 90, 19, 244, 201, 246, 13, 244, 117, 95, 84, 234, 84, 179, 2, 106, 184, 120, 80, 136, 255, 40, 176, 190, 175, 240, 135, 51, 2, 17, 0, 0, 0, 9, 73, 67, 205, 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