← previous blocknext block →recent activity
Analyzing
Block #86,833,695
10 transactions · 7 stateful · 2026-07-10 11:56:05 UTC
Parallelism
60/100
Blocked
57%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,833,695 · 10 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
2w03w14w26w39w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d07e5f7…6703
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc92cdb89…7078
0x34b655…2a6f
6 touches
3 conflicts
0x1191dbf7…8e85
0x34b655…2a6f
4 touches
1 conflict
0x231ccc13…a7c6
0x34b655…2a6f
4 touches
1 conflict
0x650e90b3…213c
0x34b655…2a6f
4 touches
1 conflict
0x650e90b3…213d
0x34b655…2a6f
4 touches
1 conflict
0x6dcb5d8d…5f07
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
3 conflicts on slot 0x7d07e5f744…8c6703
Audit this contract →
← previous block·next block →recent activity