← previous blocknext block →recent activity
Analyzing
Block #86,340,702
16 transactions · 14 stateful · 2026-07-08 04:59:16 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,340,702 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w07w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2dd7133…24d0
0x34b655…2a6f
4 touches
1 conflict
0x6b405d1c…29a4
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1c912a68…3b21
0x2a68ba…90c5
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
2 touches
0 conflicts
0x46fb9ba7…9dd0
0x34b655…2a6f
2 touches
0 conflicts
0x6f7cbcc8…8cb3
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xa2dd713374…6b24d0
Audit this contract →
← previous block·next block →recent activity