← previous blocknext block →recent activity
Analyzing
Block #90,894,069
32 transactions · 28 stateful · 2026-07-27 22:44:08 UTC
Parallelism
56/100
Blocked
64%
Avg conflicts / tx
2.09
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #90,894,069 · 32 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w09w210w311w413w514w615w716w817w919w822w1023w1124w125w226w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x0636d79f…a58c
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xa6b48d6e…0705
0x34b655…2a6f
6 touches
3 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
6 touches
3 conflicts
0x5373d1ea…127e
0x34b655…2a6f
6 touches
3 conflicts
0x5d1ac445…5233
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity