← previous blocknext block →recent activity
Analyzing
Block #86,678,300
23 transactions · 19 stateful · 2026-07-09 18:37:56 UTC
Parallelism
87/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,678,300 · 23 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
1w02w13w28w09w110w211w014w115w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca02c570…412b
0x34b655…2a6f
6 touches
3 conflicts
0x459573ed…fbbe
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x5d537073…cf27
0x34b655…2a6f
4 touches
1 conflict
0x65338476…2209
0x34b655…2a6f
4 touches
1 conflict
0x75787353…88f0
0x34b655…2a6f
4 touches
1 conflict
0x7b3da897…b268
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 0xca02c57086…5b412b
Audit this contract →
← previous block·next block →recent activity