← previous blocknext block →recent activity
Analyzing
Block #89,596,837
20 transactions · 19 stateful · 2026-07-23 07:54:59 UTC
Parallelism
80/100
Blocked
26%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,596,837 · 20 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
1w08w110w011w112w213w315w018w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06d44196…338c
0x0a2fbf…29b1
8 touches
6 conflicts
0x06d44196…338d
0x0a2fbf…29b1
8 touches
6 conflicts
0x06d44196…3390
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0xafe1c27e…a7fd
0x0a2fbf…29b1
8 touches
6 conflicts
0xafe1c27e…a7fe
0x0a2fbf…29b1
8 touches
6 conflicts
0x1bff683e…7ecb
0x754704…b603
8 touches
6 conflicts
0x55b4e430…44cb
0x754704…b603
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: 0x0a2fbf2d…f729b1
6 conflicts on slot 0x06d44196dd…08338c
Audit this contract →
← previous block·next block →recent activity