← previous blocknext block →recent activity
Analyzing
Block #86,793,427
10 transactions · 8 stateful · 2026-07-10 07:26:45 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,793,427 · 10 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
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x74550a4b…68bd
0x34b655…2a6f
8 touches
6 conflicts
0x8b87ece6…3353
0x34b655…2a6f
6 touches
3 conflicts
0xe8927855…7e59
0x34b655…2a6f
6 touches
3 conflicts
0x3f25409b…f92b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x666b28db…11f0
0x34b655…2a6f
4 touches
1 conflict
0x75588539…2c6d
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 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity