← previous blocknext block →recent activity
Analyzing
Block #87,419,207
24 transactions · 18 stateful · 2026-07-13 05:10:39 UTC
Parallelism
54/100
Blocked
61%
Avg conflicts / tx
1.54
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,419,207 · 24 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w17w28w39w410w511w612w714w815w917w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x8a35acfb…d1ae
0xb1dbf0…c0d3
8 touches
6 conflicts
0xb6dd5be0…26d6
0x34b655…2a6f
8 touches
6 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
8 touches
6 conflicts
0x71cbd5f6…e66e
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0x737fb258…1ad3
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity