← previous blocknext block →recent activity
Analyzing
Block #85,351,233
18 transactions · 16 stateful · 2026-07-03 15:01:51 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,351,233 · 18 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
2w06w07w18w09w111w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0b2a06b…4994
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xf0a21901…3895
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x4eb98096…65c2
0x34b655…2a6f
4 touches
1 conflict
0x57bb625a…286d
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
1 conflict on slot 0xe0b2a06ba6…8e4994
Audit this contract →
← previous block·next block →recent activity