Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 709d01816c74698ec687fb4a3180424a812e163347dbc48e6caa606780819217

Tx prefix hash: 92522de6e79ec9e8ba896d0158b53b714b8c07b72313685075832b4ed9f329a7
Tx public key: 7b7a820ea15d8f4c13fcf077366ed5a25da2a3fd937330d7f84715a19a710236
Timestamp: 1710961045 Timestamp [UCT]: 2024-03-20 18:57:25 Age [y:d:h:m:s]: 01:044:19:52:18
Block: 982637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293011 RingCT/type: yes/0
Extra: 017b7a820ea15d8f4c13fcf077366ed5a25da2a3fd937330d7f84715a19a710236021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1b92124ca2fb3248ac70e4042cee04174741737232e45b12cdf588f5ba25052 0.600000000000 1442746 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": 982647, "vin": [ { "gen": { "height": 982637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1b92124ca2fb3248ac70e4042cee04174741737232e45b12cdf588f5ba25052" } } ], "extra": [ 1, 123, 122, 130, 14, 161, 93, 143, 76, 19, 252, 240, 119, 54, 110, 213, 162, 93, 162, 163, 253, 147, 115, 48, 215, 248, 71, 21, 161, 154, 113, 2, 54, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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