← previous blocknext block →recent activity
Analyzing
Block #89,850,613
10 transactions · 9 stateful · 2026-07-24 06:54:27 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,850,613 · 10 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
3w04w05w16w27w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6efd452…227b
0x370e2e…63b4
8 touches
6 conflicts
0x1bff683e…7ecb
0x754704…b603
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0xbe310eec…029b
0x0a2fbf…29b1
8 touches
6 conflicts
0xbe310eec…029c
0x0a2fbf…29b1
8 touches
6 conflicts
0xcee327b0…24b8
0x0a2fbf…29b1
8 touches
6 conflicts
0xcee327b0…24b9
0x0a2fbf…29b1
8 touches
6 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: 0x370e2ee6…bd63b4
6 conflicts on slot 0xb6efd452bc…48227b
Audit this contract →
← previous block·next block →recent activity