← previous blocknext block →recent activity
Analyzing
Block #112,475,640
23 transactions · 21 stateful · 2026-10-11 13:03:42 UTC
Parallelism
65/100
Blocked
52%
Avg conflicts / tx
1.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #112,475,640 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w111w212w313w414w415w516w517w618w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d5234ea…f6a2
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x513f7af5…c728
0x34b655…2a6f
6 touches
3 conflicts
0x53057a6c…ce62
0x34b655…2a6f
4 touches
1 conflict
0x5df7cf2b…bbe5
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
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
21 conflicts on slot 0x9d5234ea2a…d6f6a2
Audit this contract →
← previous block·next block →recent activity