← previous blocknext block →recent activity
Analyzing
Block #112,583,493
23 transactions · 19 stateful · 2026-10-11 22:06:21 UTC
Parallelism
87/100
Blocked
37%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #112,583,493 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w110w111w012w115w016w117w218w220w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf788c790…e66f
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x3e1329b8…deca
0x34b655…2a6f
4 touches
1 conflict
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0xf2de8909…1eed
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x76c6ee0a…2203
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
1 conflict on slot 0xf788c79025…f8e66f
Audit this contract →
← previous block·next block →recent activity