← previous blocknext block →recent activity
Analyzing
Block #111,831,894
16 transactions · 16 stateful · 2026-10-09 07:04:47 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #111,831,894 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w110w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca608d0c…f23b
0x34b655…2a6f
4 touches
1 conflict
0xea3977c2…e82c
0x34b655…2a6f
4 touches
1 conflict
0x983c02da…cce2
0x34b655…2a6f
4 touches
1 conflict
0x2dd6a287…5261
0x34b655…2a6f
2 touches
0 conflicts
0x2fa9de7a…998d
0x34b655…2a6f
2 touches
0 conflicts
0x40d6d1e9…131e
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
1 conflict on slot 0x38c6ff017b…61689f
Audit this contract →
← previous block·next block →recent activity