← previous blocknext block →recent activity
Analyzing
Block #86,632,415
34 transactions · 26 stateful · 2026-07-09 13:30:17 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,632,415 · 34 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w213w014w115w116w218w022w129w030w131w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x4c04ce68…d007
0x34b655…2a6f
6 touches
3 conflicts
0x005b3d5e…835e
0x34b655…2a6f
4 touches
1 conflict
0x0363d65e…06d2
0x34b655…2a6f
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
4 touches
1 conflict
0x4d1d85aa…01a0
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity