← previous blocknext block →recent activity
Analyzing
Block #111,064,790
19 transactions · 19 stateful · 2026-10-06 14:43:16 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #111,064,790 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w111w212w313w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d351a9b…f2dd
0x34b655…2a6f
8 touches
6 conflicts
0xb9fc1181…d7dd
0x34b655…2a6f
8 touches
6 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
8 touches
6 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 conflicts
0xb54c8ced…5b8c
0x34b655…2a6f
6 touches
3 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0x1d351a9b20…2df2dd
Audit this contract →
← previous block·next block →recent activity