← previous blocknext block →recent activity
Analyzing
Block #89,703,782
19 transactions · 11 stateful · 2026-07-23 18:33:18 UTC
Parallelism
89/100
Blocked
9%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,703,782 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
11w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa93224c6…ced4
0x34b655…2a6f
4 touches
1 conflict
0xa93224c6…ced5
0x34b655…2a6f
4 touches
1 conflict
0xe751731d…9aa5
0x34b655…2a6f
4 touches
1 conflict
0x4e213a88…b57f
0x34b655…2a6f
3 touches
1 conflict
0x40a04862…cca2
0x065c9d…c394
2 touches
0 conflicts
0x6b5ecfb6…07a5
0x065c9d…c394
2 touches
0 conflicts
0xd35bb5ac…3586
0x065c9d…c394
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity