Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 475475dc5f67d6e1ae66ba3e8271af8a808dc2eabb215ab7316cc1476cdfe792

Tx prefix hash: d6fa8e38b4692dc6717a5a08df32a1ae26a86386def2604d00741c5d346ff846
Tx public key: 7ca5d5fe7c2b0944620a09757676597e04db25477c73721da32e4fa1c8d089b8
Timestamp: 1707825558 Timestamp [UCT]: 2024-02-13 11:59:18 Age [y:d:h:m:s]: 01:106:05:50:31
Block: 956626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337010 RingCT/type: yes/0
Extra: 017ca5d5fe7c2b0944620a09757676597e04db25477c73721da32e4fa1c8d089b802110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9a48a1f4d0b43ac4eac7b7fedbe73cebfd717ba464913bfb145cd06bec02b2c 0.600000000000 1415934 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": 956636, "vin": [ { "gen": { "height": 956626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9a48a1f4d0b43ac4eac7b7fedbe73cebfd717ba464913bfb145cd06bec02b2c" } } ], "extra": [ 1, 124, 165, 213, 254, 124, 43, 9, 68, 98, 10, 9, 117, 118, 118, 89, 126, 4, 219, 37, 71, 124, 115, 114, 29, 163, 46, 79, 161, 200, 208, 137, 184, 2, 17, 0, 0, 0, 10, 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