← previous blocknext block →recent activity
Analyzing
Block #90,788,291
22 transactions · 18 stateful · 2026-07-27 13:51:52 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,788,291 · 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
4w05w16w28w39w410w011w112w515w618w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb83ac6e4…3637
0x34b655…2a6f
8 touches
6 conflicts
0x0a42683d…6f4f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7be44262…1a9c
0x34b655…2a6f
8 touches
6 conflicts
0x42de1b4a…7fba
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
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
6 conflicts on slot 0xb83ac6e4b1…733637
Audit this contract →
← previous block·next block →recent activity