Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b0c8f4b1bb74783aed55eb4cd37445aaa8868a0785a20585f63a62265f9bbe1

Tx prefix hash: 2df353942404f4157ea2f28cfd6f58c5a6ec72d4bcb495c8e7caab2119cf75a6
Tx public key: c81cf55e616011c5f7db3327fd4c6e93386df06b683a8be20338c84f1d358bbd
Timestamp: 1710787858 Timestamp [UCT]: 2024-03-18 18:50:58 Age [y:d:h:m:s]: 01:009:08:33:36
Block: 981205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267633 RingCT/type: yes/0
Extra: 01c81cf55e616011c5f7db3327fd4c6e93386df06b683a8be20338c84f1d358bbd02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 302258a09025bdce5795a784dd1848f5d6f24c963e8a033ad289e06d7831dc4a 0.600000000000 1441298 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": 981215, "vin": [ { "gen": { "height": 981205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "302258a09025bdce5795a784dd1848f5d6f24c963e8a033ad289e06d7831dc4a" } } ], "extra": [ 1, 200, 28, 245, 94, 97, 96, 17, 197, 247, 219, 51, 39, 253, 76, 110, 147, 56, 109, 240, 107, 104, 58, 139, 226, 3, 56, 200, 79, 29, 53, 139, 189, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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