← previous blocknext block →recent activity
Analyzing
Block #89,700,510
24 transactions · 23 stateful · 2026-07-23 18:16:50 UTC
Parallelism
33/100
Blocked
70%
Avg conflicts / tx
5.04
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #89,700,510 · 24 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w712w813w914w1015w1116w1217w1318w1420w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
32 touches
120 conflicts
0x55b4e430…44cb
0x754704…b603
32 touches
120 conflicts
0x00000000…0005
0x370e2e…63b4
30 touches
105 conflicts
0x1bff683e…7ecb
0x754704…b603
30 touches
105 conflicts
0x4ba70160…0371
0x0a2fbf…29b1
22 touches
55 conflicts
0xb476cdfa…42bd
0x0a2fbf…29b1
22 touches
55 conflicts
0xb476cdfa…42be
0x0a2fbf…29b1
22 touches
55 conflicts
0xb476cdfa…42c1
0x0a2fbf…29b1
22 touches
55 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
120 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity