← previous blocknext block →recent activity
Analyzing
Block #86,957,742
14 transactions · 14 stateful · 2026-07-11 01:45:15 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,957,742 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0004
0xb1dbf0…c0d3
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x6d99ac64…0aa3
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1ac
0xb1dbf0…c0d3
4 touches
1 conflict
0x0178c2de…b37d
0xb1dbf0…c0d3
3 touches
1 conflict
0x8a35acfb…d1ad
0xb1dbf0…c0d3
3 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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity