← previous blocknext block →recent activity
Analyzing
Block #89,540,027
19 transactions · 17 stateful · 2026-07-23 01:35:30 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,540,027 · 19 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
1w02w16w07w08w19w212w315w418w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e19c9a0…7d86
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2b9c6652…d14e
0x754704…b603
4 touches
1 conflict
0x6b76ce29…0e84
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
6 conflicts on slot 0x6e19c9a020…2f7d86
Audit this contract →
← previous block·next block →recent activity