← previous blocknext block →recent activity
Analyzing
Block #90,809,127
22 transactions · 17 stateful · 2026-07-27 15:36:42 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,809,127 · 22 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
8w09w110w211w312w413w514w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xabf57eb6…416d
0x34b655…2a6f
6 touches
3 conflicts
0x22cb88f1…393e
0x34b655…2a6f
4 touches
1 conflict
0x2a1a17d1…82c0
0x34b655…2a6f
4 touches
1 conflict
0x2a21b53a…211b
0x34b655…2a6f
4 touches
1 conflict
0x48719cbe…5484
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x4f92c64e…9adc
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity