← previous blocknext block →recent activity
Analyzing
Block #89,838,326
8 transactions · 8 stateful · 2026-07-24 05:52:32 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,838,326 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d68c976…b6e6
0x34b655…2a6f
4 touches
1 conflict
0xac111fea…4e4f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0c15f714…46ab
0x34b655…2a6f
2 touches
0 conflicts
0x1191dbf7…8e85
0x34b655…2a6f
2 touches
0 conflicts
0x13a332bb…0a80
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x3dcbc94a…a380
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 0x1d68c97607…23b6e6
Audit this contract →
← previous block·next block →recent activity