Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48022d928a2dbb82ae5d72dd27f81e7ee351df36376d1ac46e45f49e60507b1e

Tx prefix hash: 77a6dc7b4052f9710edc9cfc784649927b8802e24a8e510a325ce53c55c493e5
Tx public key: c706cc80e461ee777118d786c8407fd8ce257b991d53d6c3481170eb8fa8a234
Timestamp: 1706777982 Timestamp [UCT]: 2024-02-01 08:59:42 Age [y:d:h:m:s]: 01:053:20:07:56
Block: 947919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299535 RingCT/type: yes/0
Extra: 01c706cc80e461ee777118d786c8407fd8ce257b991d53d6c3481170eb8fa8a2340211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abcf94db10437c1c848fbd6b199e4fde0e78d91d4c4a6cff721f7bbf6e6687ce 0.600000000000 1406279 of 15

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": 947929, "vin": [ { "gen": { "height": 947919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abcf94db10437c1c848fbd6b199e4fde0e78d91d4c4a6cff721f7bbf6e6687ce" } } ], "extra": [ 1, 199, 6, 204, 128, 228, 97, 238, 119, 113, 24, 215, 134, 200, 64, 127, 216, 206, 37, 123, 153, 29, 83, 214, 195, 72, 17, 112, 235, 143, 168, 162, 52, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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