← previous blocknext block →recent activity
Analyzing
Block #86,321,620
18 transactions · 17 stateful · 2026-07-08 02:51:51 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,321,620 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w112w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x000bde1a…e123
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x96dd83e6…a507
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1e78f72b…5df2
0x40c49f…2af0
2 touches
0 conflicts
0x342fbbca…d443
0x40c49f…2af0
2 touches
0 conflicts
0x525627fe…2654
0x40c49f…2af0
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 0x000bde1afc…91e123
Audit this contract →
← previous block·next block →recent activity