← previous blocknext block →recent activity
Analyzing
Block #86,796,200
21 transactions · 20 stateful · 2026-07-10 07:45:16 UTC
Parallelism
90/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,796,200 · 21 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w110w011w114w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x90e113f8…c8f9
0xc8689a…ee79
4 touches
1 conflict
0xdd70bea3…1ffe
0x3bd359…433a
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x24d58d14…f7a5
0x34b655…2a6f
4 touches
1 conflict
0x4caf91f9…8ab5
0x34b655…2a6f
4 touches
1 conflict
0x5d7d3d99…cd99
0x34b655…2a6f
4 touches
1 conflict
0x6d99ac64…0aa3
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
1 conflict on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity