← previous blocknext block →recent activity
Analyzing
Block #90,818,616
22 transactions · 18 stateful · 2026-07-27 16:24:32 UTC
Parallelism
77/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,818,616 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w09w110w211w012w117w318w419w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce3a759a…1620
0x34b655…2a6f
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x23ce455e…41ae
0x34b655…2a6f
6 touches
3 conflicts
0x2a1a17d1…82c0
0x34b655…2a6f
4 touches
1 conflict
0x3782a203…e472
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
3 conflicts on slot 0xce3a759ab7…851620
Audit this contract →
← previous block·next block →recent activity