← previous blocknext block →recent activity
Analyzing
Block #96,024,443
24 transactions · 22 stateful · 2026-08-14 21:27:41 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,024,443 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w011w312w413w516w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6b462b3…c5c9
0x34b655…2a6f
8 touches
6 conflicts
0x31616f97…1acc
0x34b655…2a6f
6 touches
3 conflicts
0x5e7e0120…7bb9
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5fab7fbe…1ce5
0x34b655…2a6f
4 touches
1 conflict
0x673e2e56…9f5d
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 0xc6b462b3d5…9ac5c9
Audit this contract →
← previous block·next block →recent activity