← previous blocknext block →recent activity
Analyzing
Block #90,791,589
15 transactions · 14 stateful · 2026-07-27 14:08:28 UTC
Parallelism
53/100
Blocked
43%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,791,589 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w211w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf9ac650a…d82d
0x34b655…2a6f
8 touches
6 conflicts
0xb733b9da…9c31
0x34b655…2a6f
6 touches
3 conflicts
0x114324a9…6d5e
0x34b655…2a6f
6 touches
3 conflicts
0x03b16972…8f62
0x34b655…2a6f
6 touches
3 conflicts
0x9ca52d19…da85
0x34b655…2a6f
6 touches
3 conflicts
0x06df379f…2653
0x34b655…2a6f
5 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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity