← previous blocknext block →recent activity
Analyzing
Block #86,331,191
22 transactions · 17 stateful · 2026-07-08 03:55:43 UTC
Parallelism
77/100
Blocked
47%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,331,191 · 22 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
2w03w18w09w113w115w116w219w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd20e39…d524
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5d537073…cf27
0x34b655…2a6f
6 touches
3 conflicts
0x8b9390da…3820
0x34b655…2a6f
6 touches
3 conflicts
0x6762cac2…3fb0
0x34b655…2a6f
4 touches
1 conflict
0x930cb996…a6f5
0x34b655…2a6f
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0xdc0c9700…ae04
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
6 conflicts on slot 0xddd20e3989…a2d524
Audit this contract →
← previous block·next block →recent activity