Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05fb858b1961eb9af9a42ed9838bfe818fd51636923beafec2b402251889d650

Tx prefix hash: 84fa567676cde4d8bbd413ba100b102b7aef226f707cee87ac20029edd4046f2
Tx public key: 586f94f41e0bb9d15f9b27a75fd197ac395ffc1045d84c5caa19f3c790ce4099
Timestamp: 1580778845 Timestamp [UCT]: 2020-02-04 01:14:05 Age [y:d:h:m:s]: 05:038:15:30:05
Block: 57968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179840 RingCT/type: yes/0
Extra: 01586f94f41e0bb9d15f9b27a75fd197ac395ffc1045d84c5caa19f3c790ce409902110000000149b77a3d000000000000000000

1 output(s) for total of 394.392614513000 dcy

stealth address amount amount idx
00: 5469088cf5af2a21d3826c37aaecdcca4fd63954885b8a3f8596d5579ac6f545 394.392614513000 107219 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": 57978, "vin": [ { "gen": { "height": 57968 } } ], "vout": [ { "amount": 394392614513, "target": { "key": "5469088cf5af2a21d3826c37aaecdcca4fd63954885b8a3f8596d5579ac6f545" } } ], "extra": [ 1, 88, 111, 148, 244, 30, 11, 185, 209, 95, 155, 39, 167, 95, 209, 151, 172, 57, 95, 252, 16, 69, 216, 76, 92, 170, 25, 243, 199, 144, 206, 64, 153, 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