← previous blocknext block →recent activity
Analyzing
Block #89,710,671
16 transactions · 15 stateful · 2026-07-23 19:08:02 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,710,671 · 16 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
2w03w14w05w113w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x51ca3051…0972
0x3bd359…433a
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
3 conflicts on slot 0x59dccbd857…c52bf6
Audit this contract →
← previous block·next block →recent activity