← previous blocknext block →recent activity
Analyzing
Block #86,454,063
31 transactions · 26 stateful · 2026-07-08 17:36:36 UTC
Parallelism
87/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,454,063 · 31 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
1w02w14w210w211w012w113w214w316w022w224w327w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0x928ffc80…6f3d
0xd32edf…ff58
5 touches
3 conflicts
0x3d405665…9c06
0x34b655…2a6f
4 touches
1 conflict
0x460a21c2…87f1
0x34b655…2a6f
4 touches
1 conflict
0x48e4ba72…3c67
0x34b655…2a6f
4 touches
1 conflict
0x5e7b24a2…294a
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity