← previous blocknext block →recent activity
Analyzing
Block #90,813,950
19 transactions · 18 stateful · 2026-07-27 16:01:03 UTC
Parallelism
84/100
Blocked
28%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,813,950 · 19 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
1w03w16w09w210w211w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26ce4189…2ffb
0x34b655…2a6f
6 touches
3 conflicts
0xc4998e49…c79d
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x3e638305…2dae
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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 0x26ce418900…052ffb
Audit this contract →
← previous block·next block →recent activity