← previous blocknext block →recent activity
Analyzing
Block #89,548,934
16 transactions · 15 stateful · 2026-07-23 02:35:04 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,548,934 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w09w111w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e19c9a0…7d86
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0xd873b8d2…fdeb
0x34b655…2a6f
4 touches
1 conflict
0xf6884b1c…8b7f
0x34b655…2a6f
4 touches
1 conflict
0x67f87cdf…e5b6
0x34b655…2a6f
4 touches
1 conflict
0x961c0cd9…0937
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
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
3 conflicts on slot 0x6e19c9a020…2f7d86
Audit this contract →
← previous block·next block →recent activity