← previous blocknext block →recent activity
Analyzing
Block #112,384,903
15 transactions · 14 stateful · 2026-10-11 05:27:10 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #112,384,903 · 15 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
6w07w110w011w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44eee1e7…3b34
0x34b655…2a6f
6 touches
3 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
4 touches
1 conflict
0x2bb0d58d…9dcf
0x34b655…2a6f
4 touches
1 conflict
0x5a9bff8a…13ca
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x99d33d1a…b0c3
0x34b655…2a6f
4 touches
1 conflict
0xc853be2d…b18f
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
3 conflicts on slot 0x44eee1e7fa…2b3b34
Audit this contract →
← previous block·next block →recent activity