← previous blocknext block →recent activity
Analyzing
Block #87,669,015
18 transactions · 15 stateful · 2026-07-14 09:01:48 UTC
Parallelism
78/100
Blocked
27%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,669,015 · 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
1w02w18w09w110w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x588c5b6a…60d2
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x2c7f2108…99fc
0x34b655…2a6f
4 touches
1 conflict
0x2c7f2108…99fd
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7634a3f4…7f24
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 0x588c5b6adb…3060d2
Audit this contract →
← previous block·next block →recent activity