← previous blocknext block →recent activity
Analyzing
Block #86,360,466
30 transactions · 23 stateful · 2026-07-08 07:11:10 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,360,466 · 30 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
3w04w15w06w111w012w116w018w219w320w424w125w226w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca4fd877…a6f3
0x40c49f…2af0
8 touches
6 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x342fbbca…d443
0x40c49f…2af0
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x09676bb2…e014
0x40c49f…2af0
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: 0x40c49f17…d22af0
6 conflicts on slot 0xca4fd87738…13a6f3
Audit this contract →
← previous block·next block →recent activity