← previous blocknext block →recent activity
Analyzing
Block #86,315,160
15 transactions · 14 stateful · 2026-07-08 02:08:39 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,315,160 · 15 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
5w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfd5b3ee0…e36f
0x34b655…2a6f
4 touches
1 conflict
0x96047c45…b64a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x72a152dd…9dff
0x16f70c…c3dd
2 touches
0 conflicts
0xd800e635…b1d7
0x34b655…2a6f
2 touches
0 conflicts
0x1a7b2836…f522
0x58e158…3d57
2 touches
0 conflicts
0x3dea5c3d…5fb8
0x58e158…3d57
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity