← previous blocknext block →recent activity
Analyzing
Block #86,363,908
17 transactions · 15 stateful · 2026-07-08 07:34:03 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,363,908 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0x7a8a74c9…6004
0xd32edf…ff58
3 touches
1 conflict
0xcfcfbf20…fbe1
0x34b655…2a6f
3 touches
1 conflict
0xde169640…e086
0x34b655…2a6f
3 touches
1 conflict
0x1c28e67a…9b1a
0x1efe02…37d6
2 touches
0 conflicts
0x81eded3e…b4dc
0x1efe02…37d6
2 touches
0 conflicts
0x995f3998…221b
0x1efe02…37d6
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 0xe06bbb2ef5…889417
Audit this contract →
← previous block·next block →recent activity