← previous blocknext block →recent activity
Analyzing
Block #96,026,311
13 transactions · 11 stateful · 2026-08-14 21:37:04 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,026,311 · 13 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
5w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fd372a1…a959
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x23253ea8…e0a4
0x34b655…2a6f
4 touches
1 conflict
0x3a8949c8…9cb2
0x34b655…2a6f
4 touches
1 conflict
0xe4eafc97…cbbf
0x34b655…2a6f
4 touches
1 conflict
0x05ae5149…f967
0x34b655…2a6f
4 touches
1 conflict
0x74462c1e…84f3
0x34b655…2a6f
4 touches
1 conflict
0x892ef2eb…89d8
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 0x9fd372a13e…ada959
Audit this contract →
← previous block·next block →recent activity