← previous blocknext block →recent activity
Analyzing
Block #112,344,541
9 transactions · 8 stateful · 2026-10-11 02:04:07 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,344,541 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2d50773…c39e
0x34b655…2a6f
4 touches
1 conflict
0x40d6d1e9…131e
0x34b655…2a6f
4 touches
1 conflict
0xc44f7c04…4b04
0x34b655…2a6f
4 touches
1 conflict
0xc4550172…3d03
0x34b655…2a6f
4 touches
1 conflict
0xd2163dd5…3739
0x34b655…2a6f
4 touches
1 conflict
0x340ccb5c…07a8
0x34b655…2a6f
2 touches
0 conflicts
0x4a31a1e5…f90a
0x34b655…2a6f
2 touches
0 conflicts
0x5aed1bd2…7afa
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xe2d5077308…5ec39e
Audit this contract →
← previous block·next block →recent activity