← previous blocknext block →recent activity
Analyzing
Block #89,384,653
21 transactions · 19 stateful · 2026-07-22 08:17:22 UTC
Parallelism
76/100
Blocked
32%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,384,653 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w111w212w314w016w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xb6ed530c…d450
0x34b655…2a6f
8 touches
6 conflicts
0xe100a7a6…cf18
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x6a4c23bd…3d81
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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity