← previous blocknext block →recent activity
Analyzing
Block #89,673,761
15 transactions · 13 stateful · 2026-07-23 16:01:41 UTC
Parallelism
87/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,673,761 · 15 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
5w06w18w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f51d069…d0b4
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xbf68b5d2…0eba
0x34b655…2a6f
4 touches
1 conflict
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0x5b145de0…367c
0xc8689a…ee79
4 touches
1 conflict
0x3d764487…266f
0x065c9d…c394
2 touches
0 conflicts
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0x87d070d0…7f3f
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 0x4f51d06968…61d0b4
Audit this contract →
← previous block·next block →recent activity