← previous blocknext block →recent activity
Analyzing
Block #89,405,429
14 transactions · 14 stateful · 2026-07-22 10:36:19 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,405,429 · 14 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
2w07w09w110w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa643d44…2122
0x34b655…2a6f
4 touches
1 conflict
0xb26fce3e…f47f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xee4fe1f7…3ead
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0x31519d10…f76b
0x34b655…2a6f
2 touches
0 conflicts
0x346e6e22…8deb
0x34b655…2a6f
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 0xaa643d4443…6c2122
Audit this contract →
← previous block·next block →recent activity