Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7794d46dc434ba5743e98cf3e90a6a7dfd1c853b4d5094412d452d9c072339c1

Tx prefix hash: adcac0086212138945db6c5d0ada7fa1ceafb37070a6b91070e4c439e9112b37
Tx public key: f87d879e6f5fc227f0e99b52dfff24e0c6cd18bd4a1dff4a5ffa8c7a797cc8b8
Timestamp: 1706272196 Timestamp [UCT]: 2024-01-26 12:29:56 Age [y:d:h:m:s]: 01:030:08:47:22
Block: 943710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282771 RingCT/type: yes/0
Extra: 01f87d879e6f5fc227f0e99b52dfff24e0c6cd18bd4a1dff4a5ffa8c7a797cc8b802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b3cc4816c107198b219754c1abe9e780e0036c2560ce99ec474f3e7b9e66179 0.600000000000 1401934 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": 943720, "vin": [ { "gen": { "height": 943710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b3cc4816c107198b219754c1abe9e780e0036c2560ce99ec474f3e7b9e66179" } } ], "extra": [ 1, 248, 125, 135, 158, 111, 95, 194, 39, 240, 233, 155, 82, 223, 255, 36, 224, 198, 205, 24, 189, 74, 29, 255, 74, 95, 250, 140, 122, 121, 124, 200, 184, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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