← previous blocknext block →recent activity
Analyzing
Block #86,619,201
47 transactions · 37 stateful · 2026-07-09 12:02:01 UTC
Parallelism
72/100
Blocked
62%
Avg conflicts / tx
1.23
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #86,619,201 · 47 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w110w011w112w014w115w216w017w118w219w320w421w522w423w532w233w734w237w842w143w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
10 touches
10 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
10 touches
10 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x70b87e4d…65d5
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity