← previous blocknext block →recent activity
Analyzing
Block #86,961,933
30 transactions · 25 stateful · 2026-07-11 02:13:16 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,961,933 · 30 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
1w04w09w010w111w218w119w020w123w225w127w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee4fe1f7…3ead
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
6 touches
3 conflicts
0x474d0d1d…14af
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x0178c2de…b37d
0xb1dbf0…c0d3
4 touches
1 conflict
0x6a248bdc…3c1b
0xb1dbf0…c0d3
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 0xee4fe1f73e…483ead
Audit this contract →
← previous block·next block →recent activity