Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 226eee95329fe8ff2ce8946938daec822d6f84b6098edbc3efb8e4ebc3fad74a

Tx prefix hash: 639e077f75af552536fa650314c262c6a068674c6740491c43d0bdadfb5767f9
Tx public key: dc70b57919c8bc7e1a89cde38947fc5779d6a22eff438f62fc9d251e65031325
Timestamp: 1582097190 Timestamp [UCT]: 2020-02-19 07:26:30 Age [y:d:h:m:s]: 04:284:19:15:45
Block: 67865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1096106 RingCT/type: yes/0
Extra: 01dc70b57919c8bc7e1a89cde38947fc5779d6a22eff438f62fc9d251e6503132502110000000212c4732d000000000000000000

1 output(s) for total of 365.709203249000 dcy

stealth address amount amount idx
00: c4c7fe19ccda2cbabf1162a71cbd8b5a077b21470a2a9ef4c856f3245024aee5 365.709203249000 125057 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": 67875, "vin": [ { "gen": { "height": 67865 } } ], "vout": [ { "amount": 365709203249, "target": { "key": "c4c7fe19ccda2cbabf1162a71cbd8b5a077b21470a2a9ef4c856f3245024aee5" } } ], "extra": [ 1, 220, 112, 181, 121, 25, 200, 188, 126, 26, 137, 205, 227, 137, 71, 252, 87, 121, 214, 162, 46, 255, 67, 143, 98, 252, 157, 37, 30, 101, 3, 19, 37, 2, 17, 0, 0, 0, 2, 18, 196, 115, 45, 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