← previous blocknext block →recent activity
Analyzing
Block #86,793,134
18 transactions · 17 stateful · 2026-07-10 07:24:48 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.94
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,793,134 · 18 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
1w02w14w05w16w29w110w211w212w313w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74550a4b…68bd
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x74550a4bea…1f68bd
Audit this contract →
← previous block·next block →recent activity