← previous blocknext block →recent activity
Analyzing
Block #86,167,867
42 transactions · 34 stateful · 2026-07-07 09:45:06 UTC
Parallelism
86/100
Blocked
53%
Avg conflicts / tx
0.98
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,167,867 · 42 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
3w08w09w110w211w312w413w415w416w017w118w219w020w121w229w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf7372c49…12b6
0xd32edf…ff58
9 touches
10 conflicts
0x65903ef9…2567
0x34b655…2a6f
8 touches
6 conflicts
0x6af306bb…2e81
0x3bd359…433a
8 touches
6 conflicts
0xce8bbe33…b72e
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity