← previous blocknext block →recent activity
Analyzing
Block #86,924,543
16 transactions · 14 stateful · 2026-07-10 22:03:28 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.75
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,924,543 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w19w210w211w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c166a56…0356
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x3c955e7e…ef5e
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4b3b0587…0912
0x34b655…2a6f
4 touches
1 conflict
0x4e10ffaa…5365
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
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 0x9c166a5658…b80356
Audit this contract →
← previous block·next block →recent activity