← previous blocknext block →recent activity
Analyzing
Block #87,753,403
15 transactions · 14 stateful · 2026-07-14 18:26:32 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,753,403 · 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
3w06w17w28w310w411w213w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x648bb928…97f2
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xcc616f7f…6178
0x34b655…2a6f
6 touches
3 conflicts
0x1737ef68…1e55
0x34b655…2a6f
4 touches
1 conflict
0x333c820d…10c1
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0x59e84008…7fac
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 0x648bb9281b…e597f2
Audit this contract →
← previous block·next block →recent activity