← previous blocknext block →recent activity
Analyzing
Block #86,233,022
40 transactions · 28 stateful · 2026-07-07 17:00:10 UTC
Parallelism
88/100
Blocked
50%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,233,022 · 40 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w09w113w214w015w118w020w221w124w127w229w331w233w034w135w237w338w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
8 touches
6 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x7b3f8378…b37d
0x34b655…2a6f
6 touches
3 conflicts
0x51aea8c3…f435
0xd32edf…ff58
5 touches
3 conflicts
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x11431f9d…42c5
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity