Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4031a5c4f3a021b3cda3b8bba1f8dca0453b410e8bf6e37a9dc74bcf377046f

Tx prefix hash: e511f5ba569f66254228924246b82bedf774dfdff7790d139d35ad7d9d22cad8
Tx public key: 7f345c29ec369c593826bb77e34f605ba86046823e3810521e983743a4b9ea15
Timestamp: 1580883602 Timestamp [UCT]: 2020-02-05 06:20:02 Age [y:d:h:m:s]: 04:363:07:28:41
Block: 58769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151041 RingCT/type: yes/0
Extra: 017f345c29ec369c593826bb77e34f605ba86046823e3810521e983743a4b9ea15021100000002b221b3d1000000000000000000

1 output(s) for total of 391.996524445000 dcy

stealth address amount amount idx
00: e1364de8cad6d2ba02e70f68ad37a2713495740d96a238214a73ee4db1f853a0 391.996524445000 108645 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": 58779, "vin": [ { "gen": { "height": 58769 } } ], "vout": [ { "amount": 391996524445, "target": { "key": "e1364de8cad6d2ba02e70f68ad37a2713495740d96a238214a73ee4db1f853a0" } } ], "extra": [ 1, 127, 52, 92, 41, 236, 54, 156, 89, 56, 38, 187, 119, 227, 79, 96, 91, 168, 96, 70, 130, 62, 56, 16, 82, 30, 152, 55, 67, 164, 185, 234, 21, 2, 17, 0, 0, 0, 2, 178, 33, 179, 209, 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