← previous blocknext block →recent activity
Analyzing
Block #86,847,198
18 transactions · 12 stateful · 2026-07-10 13:26:17 UTC
Parallelism
89/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,847,198 · 18 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
6w011w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde5fcb8e…87a1
0x34b655…2a6f
4 touches
1 conflict
0x010d4ce0…8cf0
0x34b655…2a6f
4 touches
1 conflict
0x2e30c36b…b1fa
0x34b655…2a6f
4 touches
1 conflict
0x4327afd2…1b3a
0x34b655…2a6f
4 touches
1 conflict
0x56f59993…2c32
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6e90b9b1…dca8
0x34b655…2a6f
2 touches
0 conflicts
0x7da56943…9753
0x34b655…2a6f
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 0xde5fcb8e08…cb87a1
Audit this contract →
← previous block·next block →recent activity