← previous blocknext block →recent activity
Analyzing
Block #85,101,181
21 transactions · 13 stateful · 2026-07-02 11:15:06 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,101,181 · 21 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
5w06w111w012w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x4caf91f9…8ab5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x36a81e…00b0
2 touches
0 conflicts
0x00000000…0002
0x36a81e…00b0
2 touches
0 conflicts
0x00000000…0004
0x36a81e…00b0
2 touches
0 conflicts
0xe8958a1a…07f4
0x36a81e…00b0
2 touches
0 conflicts
0xe8958a1a…07f5
0x36a81e…00b0
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
3 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity