← previous blocknext block →recent activity
Analyzing
Block #87,329,202
34 transactions · 31 stateful · 2026-07-12 19:08:41 UTC
Parallelism
85/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,329,202 · 34 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
1w04w05w16w08w010w016w117w221w122w023w124w228w131w332w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fd328f3…701f
0x34b655…2a6f
8 touches
6 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
8 touches
6 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
6 touches
3 conflicts
0xb0faf433…6fd2
0x34b655…2a6f
6 touches
3 conflicts
0xb138d087…4689
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
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 0x6fd328f36d…0d701f
Audit this contract →
← previous block·next block →recent activity