← previous blocknext block →recent activity
Analyzing
Block #85,126,203
20 transactions · 18 stateful · 2026-07-02 14:02:46 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,126,203 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w311w012w113w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x3230277c…ef39
0xc8689a…ee79
8 touches
6 conflicts
0x0934ec4c…50c8
0x34b655…2a6f
8 touches
6 conflicts
0xcffc17bc…3544
0x34b655…2a6f
8 touches
6 conflicts
0xd92a03c7…bfc7
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xd16df6cd…5532
0x40c49f…2af0
4 touches
1 conflict
0xf5310ef7…485a
0x40c49f…2af0
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity