← previous blocknext block →recent activity
Analyzing
Block #89,562,496
13 transactions · 13 stateful · 2026-07-23 04:05:38 UTC
Parallelism
62/100
Blocked
46%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,562,496 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0xbbb86e50…274f
0x0a2fbf…29b1
10 touches
10 conflicts
0xbbb86e50…2750
0x0a2fbf…29b1
10 touches
10 conflicts
0xd121bc24…efd8
0x0a2fbf…29b1
10 touches
10 conflicts
0xd121bc24…efd9
0x0a2fbf…29b1
10 touches
10 conflicts
0xd121bc24…efdc
0x0a2fbf…29b1
10 touches
10 conflicts
0x00000000…0005
0x370e2e…63b4
10 touches
10 conflicts
0x1bff683e…7ecb
0x754704…b603
10 touches
10 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
10 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity