← previous blocknext block →recent activity
Analyzing
Block #89,848,862
7 transactions · 7 stateful · 2026-07-24 06:45:38 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,848,862 · 7 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
2w03w14w26w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0x7314d56d…2b4b
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x89b9e5f7…647c
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x215f852b…14f7
0x34b655…2a6f
2 touches
0 conflicts
0x2f0fe1df…da89
0x34b655…2a6f
2 touches
0 conflicts
0x2f0fe1df…da8a
0x34b655…2a6f
2 touches
0 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: Perpl
3 conflicts on slot 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity