← previous blocknext block →recent activity
Analyzing
Block #85,221,849
11 transactions · 9 stateful · 2026-07-03 00:39:59 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,221,849 · 11 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
4w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0xd63e616b…a07d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x36d04d61…ee9d
0x34b655…2a6f
4 touches
1 conflict
0x1f5dfab2…2021
0x34b655…2a6f
2 touches
0 conflicts
0x791f4af9…3a78
0x34b655…2a6f
2 touches
0 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
2 touches
0 conflicts
0x9a3068dd…18f1
0x34b655…2a6f
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 0x68c07cb991…56ae14
Audit this contract →
← previous block·next block →recent activity