← previous blocknext block →recent activity
Analyzing
Block #85,178,443
14 transactions · 13 stateful · 2026-07-02 19:50:54 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,178,443 · 14 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
1w02w13w06w07w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44564d6…bb43
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9495bffc…46e6
0x34b655…2a6f
4 touches
1 conflict
0x6a1c69df…4442
0x40c49f…2af0
2 touches
0 conflicts
0x9676e548…754f
0x40c49f…2af0
2 touches
0 conflicts
0xdb6a3a62…f5dd
0x40c49f…2af0
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 0xb44564d6a3…0fbb43
Audit this contract →
← previous block·next block →recent activity