← previous blocknext block →recent activity
Analyzing
Block #89,784,716
8 transactions · 7 stateful · 2026-07-24 01:21:59 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,784,716 · 8 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
2w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7634a3f4…7f24
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x02ad5c19…f593
0x34b655…2a6f
2 touches
0 conflicts
0x10efb0c1…2ddc
0x34b655…2a6f
2 touches
0 conflicts
0x1ee6a8c8…026f
0x34b655…2a6f
2 touches
0 conflicts
0x2faed179…9ff9
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
1 conflict on slot 0x7634a3f42c…b47f24
Audit this contract →
← previous block·next block →recent activity