← previous blocknext block →recent activity
Analyzing
Block #86,949,388
18 transactions · 15 stateful · 2026-07-11 00:49:25 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,949,388 · 18 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
1w02w13w04w05w16w27w38w49w010w111w413w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
8 touches
6 conflicts
0xfcdb5918…2b49
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x4a6982a4…158c
0x34b655…2a6f
8 touches
6 conflicts
0xccdc32f8…72be
0x34b655…2a6f
8 touches
6 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity