← previous blocknext block →recent activity
Analyzing
Block #89,750,986
10 transactions · 8 stateful · 2026-07-23 22:31:42 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,750,986 · 10 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
4w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x100593c2…32ce
0x34b655…2a6f
4 touches
1 conflict
0x5484fc7f…a8d8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x1758bc6b…ca8f
0x34b655…2a6f
2 touches
0 conflicts
0x3c373a6d…d1ed
0x34b655…2a6f
2 touches
0 conflicts
0x466de83e…38c5
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 0x100593c20d…2632ce
Audit this contract →
← previous block·next block →recent activity