← previous blocknext block →recent activity
Analyzing
Block #96,581,040
16 transactions · 13 stateful · 2026-08-16 20:07:29 UTC
Parallelism
63/100
Blocked
46%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,581,040 · 16 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
1w02w13w24w25w38w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
12 touches
15 conflicts
0x53f393fa…00b9
0x34b655…2a6f
10 touches
10 conflicts
0x2a49f3bf…713b
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf386bff1…b350
0x34b655…2a6f
4 touches
1 conflict
0x2981b6be…7be0
0x34b655…2a6f
4 touches
1 conflict
0x32dfa6a9…12f6
0x34b655…2a6f
4 touches
1 conflict
0x7afbac8f…9cad
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
15 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity