← previous blocknext block →recent activity
Analyzing
Block #89,537,043
12 transactions · 12 stateful · 2026-07-23 01:15:34 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,537,043 · 12 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
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x63da8263…7a24
0x34b655…2a6f
4 touches
1 conflict
0xcdf7f0d2…d31c
0x34b655…2a6f
3 touches
1 conflict
0x16259dbb…fa9a
0x34b655…2a6f
2 touches
0 conflicts
0x42e917f7…ed8c
0x34b655…2a6f
2 touches
0 conflicts
0x4b90e63c…c17d
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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 0x9a3068dd84…9918f0
Audit this contract →
← previous block·next block →recent activity