← previous blocknext block →recent activity
Analyzing
Block #112,526,240
15 transactions · 15 stateful · 2026-10-11 17:18:18 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,526,240 · 15 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
1w03w04w05w17w19w110w211w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3548f3c5…af8e
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xaa3cf307…30e8
0x34b655…2a6f
6 touches
3 conflicts
0x464a82ff…41de
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x132b9de1…183b
0x34b655…2a6f
4 touches
1 conflict
0x26bbece5…6a07
0x34b655…2a6f
4 touches
1 conflict
0xbfca3cd0…5023
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
3 conflicts on slot 0x3548f3c5ae…eeaf8e
Audit this contract →
← previous block·next block →recent activity