← previous blocknext block →recent activity
Analyzing
Block #86,247,109
27 transactions · 22 stateful · 2026-07-07 18:34:18 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,247,109 · 27 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
2w03w14w05w110w211w115w216w319w020w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd30f9e74…d404
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0x101946a1…c524
0x34b655…2a6f
4 touches
1 conflict
0x48ab8930…9e8e
0x34b655…2a6f
4 touches
1 conflict
0x59dbc306…f976
0x34b655…2a6f
4 touches
1 conflict
0x6637e421…af93
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