← previous blocknext block →recent activity
Analyzing
Block #86,850,043
32 transactions · 23 stateful · 2026-07-10 13:45:18 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,850,043 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w09w113w114w215w220w328w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0222913d…cf66
0x34b655…2a6f
4 touches
1 conflict
0x0f21840f…6cde
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3a2a8323…3f40
0x34b655…2a6f
4 touches
1 conflict
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
1 conflict on slot 0x0222913d72…7ecf66
Audit this contract →
← previous block·next block →recent activity