← previous blocknext block →recent activity
Analyzing
Block #86,625,599
57 transactions · 44 stateful · 2026-07-09 12:44:41 UTC
Parallelism
74/100
Blocked
61%
Avg conflicts / tx
2.21
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,625,599 · 57 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w210w311w012w116w017w118w219w320w421w522w623w724w825w926w1027w1128w1229w1331w238w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
28 touches
91 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x12573732…e891
0x34b655…2a6f
8 touches
6 conflicts
0x15a8dcd6…2c36
0x34b655…2a6f
8 touches
6 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x22bc4ea4…5c8a
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
91 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity