← previous blocknext block →recent activity
Analyzing
Block #86,625,756
21 transactions · 20 stateful · 2026-07-09 12:45:44 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,625,756 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w09w210w311w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7013be2…c0a8
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf6dfaa05…2749
0x34b655…2a6f
6 touches
3 conflicts
0x65e795ca…0320
0x34b655…2a6f
4 touches
1 conflict
0x794443d1…2190
0x34b655…2a6f
4 touches
1 conflict
0x8eda4743…87e6
0x34b655…2a6f
4 touches
1 conflict
0xafb2524a…0ce4
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
10 conflicts on slot 0xa7013be2a1…9ac0a8
Audit this contract →
← previous block·next block →recent activity