← previous blocknext block →recent activity
Analyzing
Block #112,338,477
17 transactions · 14 stateful · 2026-10-11 01:33:36 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,338,477 · 17 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
13w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb50fa67a…de28
0x34b655…2a6f
4 touches
1 conflict
0x0d69b170…f45b
0x34b655…2a6f
4 touches
1 conflict
0x0f3f8427…9852
0x34b655…2a6f
4 touches
1 conflict
0x4c94c9fc…e946
0x34b655…2a6f
4 touches
1 conflict
0x3643741b…109c
0x34b655…2a6f
2 touches
0 conflicts
0x366a19b0…f065
0x34b655…2a6f
2 touches
0 conflicts
0x4ef288eb…015a
0x34b655…2a6f
2 touches
0 conflicts
0x5b8c24d0…86c9
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 0xb50fa67aee…7ade28
Audit this contract →
← previous block·next block →recent activity