← previous blocknext block →recent activity
Analyzing
Block #89,847,908
15 transactions · 13 stateful · 2026-07-24 06:40:50 UTC
Parallelism
67/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,847,908 · 15 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
4w06w17w28w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ca2a6c3…ab80
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1191dbf7…8e85
0x34b655…2a6f
4 touches
1 conflict
0x13046c0b…62c9
0x34b655…2a6f
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xfe2577ac…677b
0x34b655…2a6f
4 touches
1 conflict
0xd3d34ee4…cc85
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 0x4ca2a6c35e…0eab80
Audit this contract →
← previous block·next block →recent activity