Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f93cd61769c5933aa97e16972ecce1f373566e8dc99956896eb651fa294654ed

Tx prefix hash: fdfa92030994247640e8e503e75b7aab5d4f5c89c3e41a6df3905f9e60222370
Tx public key: cfc4d2ce1b6ae5a066dbdef435078b6a4d53b738fe4c7f4c1f0251259da61bfd
Timestamp: 1581000695 Timestamp [UCT]: 2020-02-06 14:51:35 Age [y:d:h:m:s]: 04:144:12:36:58
Block: 60005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 994497 RingCT/type: yes/0
Extra: 01cfc4d2ce1b6ae5a066dbdef435078b6a4d53b738fe4c7f4c1f0251259da61bfd021100000004d81c26c0000000000000000000

1 output(s) for total of 388.310687712000 dcy

stealth address amount amount idx
00: e4427153bea801255c95792e8fbcee3efe0727a2b006235c44eb974e324cb0e9 388.310687712000 110661 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": 60015, "vin": [ { "gen": { "height": 60005 } } ], "vout": [ { "amount": 388310687712, "target": { "key": "e4427153bea801255c95792e8fbcee3efe0727a2b006235c44eb974e324cb0e9" } } ], "extra": [ 1, 207, 196, 210, 206, 27, 106, 229, 160, 102, 219, 222, 244, 53, 7, 139, 106, 77, 83, 183, 56, 254, 76, 127, 76, 31, 2, 81, 37, 157, 166, 27, 253, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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