← previous blocknext block →recent activity
Analyzing
Block #89,854,681
18 transactions · 17 stateful · 2026-07-24 07:14:54 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,854,681 · 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
1w02w05w07w19w210w011w112w213w114w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x370e2e…63b4
6 touches
3 conflicts
0x381850b8…2779
0x370e2e…63b4
6 touches
3 conflicts
0xe56bbf38…b560
0x0a2fbf…29b1
6 touches
3 conflicts
0x0d4d8195…563c
0x0a2fbf…29b1
6 touches
3 conflicts
0x0d4d8195…563d
0x0a2fbf…29b1
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x0a2fbf…29b1
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: 0x370e2ee6…bd63b4
3 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity