← previous blocknext block →recent activity
Analyzing
Block #90,801,883
18 transactions · 16 stateful · 2026-07-27 15:00:16 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,801,883 · 18 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
3w05w16w17w28w310w013w014w215w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0649b8e0…c704
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x12978194…d32f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1d68c976…b6e6
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x32409e80…a396
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x0649b8e009…10c704
Audit this contract →
← previous block·next block →recent activity