← previous blocknext block →recent activity
Analyzing
Block #89,871,309
19 transactions · 14 stateful · 2026-07-24 08:38:33 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,871,309 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w29w311w412w516w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x370e2e…63b4
12 touches
15 conflicts
0x347317f9…7938
0x0a2fbf…29b1
12 touches
15 conflicts
0x9055352a…a6c6
0x0a2fbf…29b1
12 touches
15 conflicts
0x9055352a…a6c7
0x0a2fbf…29b1
12 touches
15 conflicts
0x9055352a…a6ca
0x0a2fbf…29b1
12 touches
15 conflicts
0x00000000…0006
0x0a2fbf…29b1
12 touches
15 conflicts
0x1bff683e…7ecb
0x754704…b603
12 touches
15 conflicts
0x55b4e430…44cb
0x754704…b603
12 touches
15 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
15 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity