Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 340890653c6f2e7c0ee1d01fcb12d3b41db0cf56348ed04a9b8c25d3b2f1da44

Tx prefix hash: 68108156301f37f4067b4e1ceea0c1922094d9a81adcac12a70f773d017ad8c1
Tx public key: cd3d703d92b593c5b7befb91595eda04a8f7cf2718d8c43f93be3f5a89e94291
Timestamp: 1583540816 Timestamp [UCT]: 2020-03-07 00:26:56 Age [y:d:h:m:s]: 04:338:07:24:58
Block: 78032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135906 RingCT/type: yes/0
Extra: 01cd3d703d92b593c5b7befb91595eda04a8f7cf2718d8c43f93be3f5a89e942910211000000414ac5aa02000000000000000000

1 output(s) for total of 338.414049048000 dcy

stealth address amount amount idx
00: 1d081dc6f085981e186bcf3a4ef198bf6439c7567b039de41f9c7371260b2172 338.414049048000 143289 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": 78042, "vin": [ { "gen": { "height": 78032 } } ], "vout": [ { "amount": 338414049048, "target": { "key": "1d081dc6f085981e186bcf3a4ef198bf6439c7567b039de41f9c7371260b2172" } } ], "extra": [ 1, 205, 61, 112, 61, 146, 181, 147, 197, 183, 190, 251, 145, 89, 94, 218, 4, 168, 247, 207, 39, 24, 216, 196, 63, 147, 190, 63, 90, 137, 233, 66, 145, 2, 17, 0, 0, 0, 65, 74, 197, 170, 2, 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