← previous blocknext block →recent activity
Analyzing
Block #86,673,966
38 transactions · 25 stateful · 2026-07-09 18:09:03 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,673,966 · 38 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
9w010w115w016w117w219w322w123w424w226w527w129w235w436w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0xa3dc0a62…126a
0x34b655…2a6f
4 touches
1 conflict
0xa94f6641…e11c
0x34b655…2a6f
4 touches
1 conflict
0xb4bd7725…9cc5
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity