← previous blocknext block →recent activity
Analyzing
Block #86,677,931
20 transactions · 16 stateful · 2026-07-09 18:35:28 UTC
Parallelism
90/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,677,931 · 20 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
6w07w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36203b4b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x36203b4b…8a06
0x34b655…2a6f
4 touches
1 conflict
0x273c2a35…7513
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1ea2b1f6…1d58
0x34b655…2a6f
2 touches
0 conflicts
0x2e095751…39dc
0x34b655…2a6f
2 touches
0 conflicts
0x3771980f…f352
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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 0x36203b4b78…f28a05
Audit this contract →
← previous block·next block →recent activity