← previous blocknext block →recent activity
Analyzing
Block #86,883,316
16 transactions · 16 stateful · 2026-07-10 17:27:55 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,883,316 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w17w28w310w411w012w114w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9bfadad9…7484
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x21683d77…4e07
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x3093e806…bde2
0x34b655…2a6f
6 touches
3 conflicts
0x9427219b…5f2b
0x34b655…2a6f
6 touches
3 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x9bfadad9a2…737484
Audit this contract →
← previous block·next block →recent activity