← previous blocknext block →recent activity
Analyzing
Block #89,388,040
25 transactions · 23 stateful · 2026-07-22 08:40:02 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,388,040 · 25 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
1w02w15w06w17w28w09w111w215w216w317w018w219w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x1bff683e…7ecb
0x754704…b603
8 touches
6 conflicts
0x55b4e430…44cb
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x6793cfc5…3328
0x0a2fbf…29b1
8 touches
6 conflicts
0x6793cfc5…3329
0x0a2fbf…29b1
8 touches
6 conflicts
0xdb5b157b…f61b
0x0a2fbf…29b1
8 touches
6 conflicts
0xdb5b157b…f61c
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 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity