← previous blocknext block →recent activity
Analyzing
Block #86,487,757
30 transactions · 27 stateful · 2026-07-08 21:22:04 UTC
Parallelism
87/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,487,757 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w08w19w210w115w319w020w121w022w125w027w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd720bba7…7467
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4b268018…02fb
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0001
0xa2c1a0…7201
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
6 conflicts on slot 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity