← previous blocknext block →recent activity

Analyzing

Block #95,023,839

16 transactions · 14 stateful · 2026-08-11 09:18:54 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,023,839  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x7f36c79c…20dd

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x6c26d635…1bbf

0x34b655…2a6f

4 touches
1 conflict

0xffc3de0b…e501

0x99c7a7…8bf0

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x45ea7a97…bbb3

0x34b655…2a6f

4 touches
1 conflict

0xfaa5c672…5681

0x34b655…2a6f

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Perpl

6 conflicts on slot 0x7f36c79c6f…e520dd

← previous block·next block →recent activity