← previous blocknext block →recent activity
Analyzing
Block #89,840,237
14 transactions · 13 stateful · 2026-07-24 06:02:11 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,840,237 · 14 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
10w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3acd75ca…2d70
0x34b655…2a6f
6 touches
3 conflicts
0xa4dc1328…d42d
0x34b655…2a6f
6 touches
3 conflicts
0x74eeff73…4115
0x34b655…2a6f
4 touches
1 conflict
0x8c5ef7e9…05f7
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xca141356…d205
0x34b655…2a6f
4 touches
1 conflict
0x6dd9ceaf…0cd2
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity