← previous blocknext block →recent activity
Analyzing
Block #86,487,707
18 transactions · 17 stateful · 2026-07-08 21:21:44 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,487,707 · 18 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
2w04w15w213w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2207d3d…59ce
0x34b655…2a6f
8 touches
6 conflicts
0x9f40a209…1193
0x34b655…2a6f
4 touches
1 conflict
0xd27ba48f…a20f
0x34b655…2a6f
4 touches
1 conflict
0xf0efe7a0…0643
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0001
0xa2c1a0…7201
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x922c7ebd…6600
0xc8689a…ee79
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 0xc2207d3d4e…b259ce
Audit this contract →
← previous block·next block →recent activity