← previous blocknext block →recent activity
Analyzing
Block #89,707,393
18 transactions · 17 stateful · 2026-07-23 18:51:30 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,707,393 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w18w19w210w311w212w315w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x062b2598…4e28
0x43cf54…7777
6 touches
3 conflicts
0x0dbf9688…c6cf
0x43cf54…7777
6 touches
3 conflicts
0x99c5409a…25b7
0x34b655…2a6f
6 touches
3 conflicts
0x6f845aff…9fc9
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x4b6ce4…7f37
6 touches
3 conflicts
0x00000000…0003
0x4b6ce4…7f37
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity