← previous blocknext block →recent activity
Analyzing
Block #86,836,714
16 transactions · 15 stateful · 2026-07-10 12:16:16 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,836,714 · 16 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
1w02w14w05w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f251b96…6054
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0x24d58d14…f7a5
0x34b655…2a6f
4 touches
1 conflict
0xe72db68c…8778
0xd32edf…ff58
3 touches
1 conflict
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065e
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x5f251b962b…3e6054
Audit this contract →
← previous block·next block →recent activity