← previous blocknext block →recent activity
Analyzing
Block #112,486,991
13 transactions · 12 stateful · 2026-10-11 14:00:48 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,486,991 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4550172…3d03
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdd9dc4b3…73b8
0x34b655…2a6f
4 touches
1 conflict
0x9026bdfc…b5a7
0x34b655…2a6f
4 touches
1 conflict
0xd88e947f…ed40
0x34b655…2a6f
4 touches
1 conflict
0x18861dbf…968e
0x34b655…2a6f
4 touches
1 conflict
0xe09e365c…b22d
0x34b655…2a6f
4 touches
1 conflict
0xce307d4a…b8d8
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
6 conflicts on slot 0xc4550172b5…c13d03
Audit this contract →
← previous block·next block →recent activity