← previous blocknext block →recent activity
Analyzing
Block #86,294,963
19 transactions · 14 stateful · 2026-07-07 23:53:41 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,294,963 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w210w011w117w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x833cb3bd…e138
0x34b655…2a6f
6 touches
3 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0003
0x019883…2a9a
4 touches
1 conflict
0x44ad89ba…cf83
0x0cc9b2…7777
4 touches
1 conflict
0x99a3a7c1…1e2b
0x0cc9b2…7777
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x38232bf9…db72
0x34b655…2a6f
4 touches
1 conflict
0x620b761c…270e
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 0x833cb3bdde…8be138
Audit this contract →
← previous block·next block →recent activity