← previous blocknext block →recent activity
Analyzing
Block #89,526,148
30 transactions · 26 stateful · 2026-07-23 00:02:55 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,526,148 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w07w08w19w210w113w014w115w216w018w121w323w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xeaced15b…2221
0x754704…b603
6 touches
3 conflicts
0x01d583a1…3405
0xd32edf…ff58
5 touches
3 conflicts
0x10797f0b…439a
0x34b655…2a6f
4 touches
1 conflict
0x278178c4…1f3c
0x34b655…2a6f
4 touches
1 conflict
0x78304d94…9e5e
0x34b655…2a6f
4 touches
1 conflict
0x861e5aef…d32c
0x34b655…2a6f
4 touches
1 conflict
0xbaf6ed88…c179
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity