← previous blocknext block →recent activity
Analyzing
Block #86,703,968
12 transactions · 11 stateful · 2026-07-09 21:29:14 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,703,968 · 12 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
10w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89c7ec3b…85ba
0x34b655…2a6f
4 touches
1 conflict
0x9de95c94…61c3
0x34b655…2a6f
4 touches
1 conflict
0xb0560167…6a76
0x34b655…2a6f
4 touches
1 conflict
0xb25fa8e2…c9ef
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1e04c5ec…8d51
0x34b655…2a6f
2 touches
0 conflicts
0x37d6e698…8f12
0x34b655…2a6f
2 touches
0 conflicts
0x4f17dc85…c493
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 0x89c7ec3b6a…8e85ba
Audit this contract →
← previous block·next block →recent activity