← previous blocknext block →recent activity
Analyzing
Block #86,331,014
30 transactions · 22 stateful · 2026-07-08 03:54:32 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,331,014 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w09w115w016w118w219w220w322w126w027w128w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca2926e0…61b5
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe5a9274d…78d7
0x34b655…2a6f
6 touches
3 conflicts
0xfa42f7fc…90f9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
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
10 conflicts on slot 0xca2926e0af…1961b5
Audit this contract →
← previous block·next block →recent activity