← previous blocknext block →recent activity
Analyzing
Block #89,846,121
16 transactions · 14 stateful · 2026-07-24 06:31:51 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,846,121 · 16 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
4w07w08w110w112w213w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0xd201f2b2…8a43
0x34b655…2a6f
8 touches
6 conflicts
0x90d21b59…307f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x29871f90…45bb
0x34b655…2a6f
4 touches
1 conflict
0x374e3403…4546
0x34b655…2a6f
4 touches
1 conflict
0x3fc40870…7ef4
0x34b655…2a6f
4 touches
1 conflict
0x4bb0bfb0…8f11
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 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity