← previous blocknext block →recent activity
Analyzing
Block #89,278,283
12 transactions · 11 stateful · 2026-07-21 20:26:26 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,278,283 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w39w010w111w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6839f88…191f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0xd6839f88bb…a1191f
Audit this contract →
← previous block·next block →recent activity