Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4943f6e59419a73356bb3c190cf45472249a7fc8a0af4e75bc759ec1bbcc3b1e

Tx prefix hash: eac7c9873fca91da973a4c9c113f57333166c4c3eed8f64bf16b00c5a487d584
Tx public key: 4ea48a478f8e8f24591c10d5be846f9f79cc4e85932f5d12686742276f686efe
Timestamp: 1711784254 Timestamp [UCT]: 2024-03-30 07:37:34 Age [y:d:h:m:s]: 01:029:20:26:44
Block: 989463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282304 RingCT/type: yes/0
Extra: 014ea48a478f8e8f24591c10d5be846f9f79cc4e85932f5d12686742276f686efe02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7527a9e078d78c1f157ac81dc98ebe80d1789f41194afbce8f7427bc571bea6 0.600000000000 1449760 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": 989473, "vin": [ { "gen": { "height": 989463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7527a9e078d78c1f157ac81dc98ebe80d1789f41194afbce8f7427bc571bea6" } } ], "extra": [ 1, 78, 164, 138, 71, 143, 142, 143, 36, 89, 28, 16, 213, 190, 132, 111, 159, 121, 204, 78, 133, 147, 47, 93, 18, 104, 103, 66, 39, 111, 104, 110, 254, 2, 17, 0, 0, 0, 10, 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