← previous blocknext block →recent activity
Analyzing
Block #86,925,648
25 transactions · 21 stateful · 2026-07-10 22:10:52 UTC
Parallelism
84/100
Blocked
52%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,925,648 · 25 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
1w02w13w24w05w16w28w09w111w012w113w117w218w323w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7babfe9a…ff96
0x34b655…2a6f
8 touches
6 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x44525e13…86ea
0x34b655…2a6f
4 touches
1 conflict
0x45597879…8174
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x5083996d…88e4
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
6 conflicts on slot 0x7babfe9a22…93ff96
Audit this contract →
← previous block·next block →recent activity