← previous blocknext block →recent activity
Analyzing
Block #111,071,748
26 transactions · 21 stateful · 2026-10-06 15:18:25 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #111,071,748 · 26 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
7w08w111w012w113w114w219w020w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0abbeb0f…b518
0x34b655…2a6f
6 touches
3 conflicts
0xf0668f0f…ce1d
0x34b655…2a6f
4 touches
1 conflict
0xf8ba9581…ad55
0x34b655…2a6f
4 touches
1 conflict
0x7954ece9…fef0
0x34b655…2a6f
4 touches
1 conflict
0x821bad75…54fc
0x34b655…2a6f
4 touches
1 conflict
0x89a8907a…3403
0x34b655…2a6f
4 touches
1 conflict
0xbfd56fdb…41c9
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity