← previous blocknext block →recent activity
Analyzing
Block #112,486,761
26 transactions · 25 stateful · 2026-10-11 13:59:39 UTC
Parallelism
85/100
Blocked
28%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,486,761 · 26 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
4w08w09w110w111w012w113w214w315w317w022w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736e5881…92f7
0x34b655…2a6f
8 touches
6 conflicts
0x4fb22186…c457
0x34b655…2a6f
8 touches
6 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x53057a6c…ce62
0x34b655…2a6f
4 touches
1 conflict
0x788c42bf…d12d
0x34b655…2a6f
4 touches
1 conflict
0x7a0dfad1…210c
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
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 0x736e58813d…b592f7
Audit this contract →
← previous block·next block →recent activity