← previous blocknext block →recent activity
Analyzing
Block #86,947,079
15 transactions · 14 stateful · 2026-07-11 00:34:00 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,947,079 · 15 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
2w03w14w19w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
4 touches
1 conflict
0x9427219b…5f2b
0x34b655…2a6f
4 touches
1 conflict
0x94ed0437…073c
0x34b655…2a6f
4 touches
1 conflict
0xa412324b…90aa
0x34b655…2a6f
4 touches
1 conflict
0xd1db601b…c70d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xded7831c…3c4a
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
3 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity