← previous blocknext block →recent activity
Analyzing
Block #89,570,331
15 transactions · 14 stateful · 2026-07-23 04:58:03 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,570,331 · 15 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
3w06w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d7b3d63…c856
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x608c0017…8138
0x065c9d…c394
2 touches
0 conflicts
0xc350c715…a6f8
0x065c9d…c394
2 touches
0 conflicts
0xd26325c3…e01c
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 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
1 conflict on slot 0x2d7b3d637a…13c856
Audit this contract →
← previous block·next block →recent activity