← previous blocknext block →recent activity
Analyzing
Block #87,420,689
15 transactions · 13 stateful · 2026-07-13 05:20:33 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,420,689 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w07w18w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f6fc26c…3e34
0x34b655…2a6f
6 touches
3 conflicts
0x11d629eb…bcd9
0x34b655…2a6f
6 touches
3 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x9a36cb2e…0929
0x34b655…2a6f
4 touches
1 conflict
0x9d056e3f…e00f
0x34b655…2a6f
4 touches
1 conflict
0xa95c7ce2…5413
0x34b655…2a6f
4 touches
1 conflict
0xb0a33dea…614c
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 0x6f6fc26c68…133e34
Audit this contract →
← previous block·next block →recent activity