← previous blocknext block →recent activity
Analyzing
Block #90,855,166
11 transactions · 11 stateful · 2026-07-27 19:28:23 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,855,166 · 11 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
1w02w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbca4de0c…577c
0x34b655…2a6f
4 touches
1 conflict
0x15554b7b…e30e
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x9a287655…f785
0x34b655…2a6f
4 touches
1 conflict
0x11a90f82…8bb6
0x34b655…2a6f
2 touches
0 conflicts
0x1703647e…b2c4
0x34b655…2a6f
2 touches
0 conflicts
0x22f59c1f…c61d
0x34b655…2a6f
2 touches
0 conflicts
0x365bd58a…0eb5
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 0xbca4de0cd0…27577c
Audit this contract →
← previous block·next block →recent activity