← previous blocknext block →recent activity
Analyzing
Block #89,736,902
14 transactions · 14 stateful · 2026-07-23 21:20:31 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,736,902 · 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
2w03w14w011w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x1787d460…e891
0x34b655…2a6f
4 touches
1 conflict
0x1d644120…7907
0x34b655…2a6f
4 touches
1 conflict
0x2ac796c1…5bbc
0x34b655…2a6f
4 touches
1 conflict
0x33967383…de4d
0x34b655…2a6f
4 touches
1 conflict
0x37532299…e35f
0x34b655…2a6f
4 touches
1 conflict
0x469bc06d…1433
0x34b655…2a6f
4 touches
1 conflict
0x4f267385…cc89
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity