← previous blocknext block →recent activity
Analyzing
Block #86,925,047
15 transactions · 12 stateful · 2026-07-10 22:06:50 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,925,047 · 15 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
3w06w17w28w39w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6dcef4f…39dd
0x34b655…2a6f
6 touches
3 conflicts
0x6bd6b33e…9557
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x313d3d93…4aa2
0x34b655…2a6f
4 touches
1 conflict
0x4b3b0587…0912
0x34b655…2a6f
4 touches
1 conflict
0x5067865d…de75
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7babfe9a…ff96
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 0xc6dcef4ffa…3039dd
Audit this contract →
← previous block·next block →recent activity