← previous blocknext block →recent activity
Analyzing
Block #112,612,360
13 transactions · 12 stateful · 2026-10-12 00:31:35 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,612,360 · 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
7w09w110w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xcf352dfa…2b99
0x34b655…2a6f
4 touches
1 conflict
0xf6df2daa…025a
0x34b655…2a6f
4 touches
1 conflict
0x364161de…acf4
0x34b655…2a6f
4 touches
1 conflict
0x3afae44c…e494
0x34b655…2a6f
4 touches
1 conflict
0x44631748…f48a
0x34b655…2a6f
4 touches
1 conflict
0x468c69db…851e
0x34b655…2a6f
4 touches
1 conflict
0x4bdc06d3…c77e
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity