← previous blocknext block →recent activity
Analyzing
Block #85,170,839
13 transactions · 12 stateful · 2026-07-02 19:00:12 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,170,839 · 13 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebd8c9b0…2ba6
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x7a45344c…c168
0x34b655…2a6f
6 touches
3 conflicts
0x52163873…f09f
0x34b655…2a6f
6 touches
3 conflicts
0x16d61f62…015b
0x34b655…2a6f
4 touches
1 conflict
0x17252dbe…94d8
0x34b655…2a6f
4 touches
1 conflict
0x43db9f49…ac4d
0x34b655…2a6f
4 touches
1 conflict
0x922c7ebd…6600
0xc8689a…ee79
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
3 conflicts on slot 0xebd8c9b046…352ba6
Audit this contract →
← previous block·next block →recent activity