← previous blocknext block →recent activity
Analyzing
Block #90,686,365
7 transactions · 6 stateful · 2026-07-27 05:19:07 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,686,365 · 7 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
1w02w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x5f917ce8…a3c3
0x34b655…2a6f
2 touches
0 conflicts
0x64379f29…8972
0x34b655…2a6f
2 touches
0 conflicts
0x81561f70…fefd
0x34b655…2a6f
2 touches
0 conflicts
0x85c84f98…06d7
0x34b655…2a6f
2 touches
0 conflicts
0x88925bd4…b7b9
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity