← previous blocknext block →recent activity
Analyzing
Block #89,414,257
36 transactions · 26 stateful · 2026-07-22 11:35:20 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.53
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,414,257 · 36 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
1w02w05w06w19w110w118w019w120w221w323w226w429w532w533w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4681609f…6493
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x46cb45de…a568
0x188d58…ea8e
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x46cb45de…a566
0x188d58…ea8e
6 touches
3 conflicts
0x8a2f9a36…fb4a
0xfa32f9…f3f0
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
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 0x4681609fd4…e96493
Audit this contract →
← previous block·next block →recent activity