Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 944d6ea5be74402515ce176de8eec94e75f231a880b3a791c53d7161e5ca1d4e

Tx prefix hash: 1addd655ef84252f6ff8acdc94bfe0824836639978e2b1bf1e8ab82100d1fe4b
Tx public key: b6396d44a01d1c1a77cc3794c532fa82ac3bb7b5a70530ab31ec8a1a25de0135
Timestamp: 1708283748 Timestamp [UCT]: 2024-02-18 19:15:48 Age [y:d:h:m:s]: 01:079:14:57:57
Block: 960424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317957 RingCT/type: yes/0
Extra: 01b6396d44a01d1c1a77cc3794c532fa82ac3bb7b5a70530ab31ec8a1a25de01350211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c069d7de55092d586d5acd330655e688643be7caa55b121dd8c74519e1f25b8 0.600000000000 1419989 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": 960434, "vin": [ { "gen": { "height": 960424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c069d7de55092d586d5acd330655e688643be7caa55b121dd8c74519e1f25b8" } } ], "extra": [ 1, 182, 57, 109, 68, 160, 29, 28, 26, 119, 204, 55, 148, 197, 50, 250, 130, 172, 59, 183, 181, 167, 5, 48, 171, 49, 236, 138, 26, 37, 222, 1, 53, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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