← previous blocknext block →recent activity
Analyzing
Block #86,387,384
17 transactions · 16 stateful · 2026-07-08 10:11:14 UTC
Parallelism
76/100
Blocked
25%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,387,384 · 17 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
5w07w112w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfe3d37ee…6e67
0x34b655…2a6f
4 touches
1 conflict
0xe18c1d5a…135f
0x34b655…2a6f
4 touches
1 conflict
0xe229ddc9…1470
0x34b655…2a6f
4 touches
1 conflict
0xee4fe1f7…3ead
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x16a8cd0c…27bd
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity