← previous blocknext block →recent activity
Analyzing
Block #90,706,171
16 transactions · 15 stateful · 2026-07-27 06:58:44 UTC
Parallelism
81/100
Blocked
53%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,706,171 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w08w110w111w112w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0e391a2e…d634
0x34b655…2a6f
4 touches
1 conflict
0x1104dd1a…dbcd
0x34b655…2a6f
4 touches
1 conflict
0x18ae81b0…28c3
0x34b655…2a6f
4 touches
1 conflict
0x1bdb47ec…864a
0x34b655…2a6f
4 touches
1 conflict
0x1bdb47ec…864b
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity