← previous blocknext block →recent activity
Analyzing
Block #89,848,478
10 transactions · 8 stateful · 2026-07-24 06:43:42 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,848,478 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96bbcfed…8a7a
0x34b655…2a6f
6 touches
3 conflicts
0xbdc75c16…0d48
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3d04f706…b354
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4a3ce847…82c4
0x34b655…2a6f
4 touches
1 conflict
0x5571e830…9cea
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
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 0x96bbcfed3e…438a7a
Audit this contract →
← previous block·next block →recent activity