← previous blocknext block →recent activity
Analyzing
Block #86,316,338
12 transactions · 12 stateful · 2026-07-08 02:16:31 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,316,338 · 12 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
2w03w14w06w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d31edd8…81c6
0x34b655…2a6f
6 touches
3 conflicts
0x56153262…21ce
0x34b655…2a6f
6 touches
3 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
6 touches
3 conflicts
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xec798b0d…0dec
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xb9d94587…9911
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
3 conflicts on slot 0x6d31edd87c…9e81c6
Audit this contract →
← previous block·next block →recent activity