← previous blocknext block →recent activity
Analyzing
Block #87,503,703
14 transactions · 11 stateful · 2026-07-13 14:35:39 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,503,703 · 14 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
2w07w19w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
6 touches
3 conflicts
0xff3f0db4…ac9f
0x34b655…2a6f
4 touches
1 conflict
0xddd7607e…9b4b
0x34b655…2a6f
4 touches
1 conflict
0xe3fbd09c…9f30
0x34b655…2a6f
4 touches
1 conflict
0xe4af56d6…5a50
0x34b655…2a6f
4 touches
1 conflict
0xe5a38e46…a68c
0x34b655…2a6f
4 touches
1 conflict
0x05b1b07a…7a99
0x34b655…2a6f
4 touches
1 conflict
0x3dcbc94a…a380
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 0xb5a3b1be7c…288122
Audit this contract →
← previous block·next block →recent activity