Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c9f2859a927a0e550c0811ed346f998f52cc9b6da1f5feb426d9e818fb27ec1

Tx prefix hash: 2a2f9f8b6180319d3dc89d93a9372539b6b29a8d9a6e93741118559feaf9e647
Tx public key: 8494ebdc16b2e176a5f2379d8224cdf1e3501e48819a2d9f21a0fe163f157b25
Timestamp: 1713312398 Timestamp [UCT]: 2024-04-17 00:06:38 Age [y:d:h:m:s]: 01:030:07:01:06
Block: 1002098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282631 RingCT/type: yes/0
Extra: 018494ebdc16b2e176a5f2379d8224cdf1e3501e48819a2d9f21a0fe163f157b250211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6135c4d5622a343f4aba57076c7fb5351f3c2aa38bb04b062aeceddc34a9716 0.600000000000 1462612 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": 1002108, "vin": [ { "gen": { "height": 1002098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6135c4d5622a343f4aba57076c7fb5351f3c2aa38bb04b062aeceddc34a9716" } } ], "extra": [ 1, 132, 148, 235, 220, 22, 178, 225, 118, 165, 242, 55, 157, 130, 36, 205, 241, 227, 80, 30, 72, 129, 154, 45, 159, 33, 160, 254, 22, 63, 21, 123, 37, 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