← previous blocknext block →recent activity
Analyzing
Block #87,726,591
14 transactions · 13 stateful · 2026-07-14 15:27:10 UTC
Parallelism
50/100
Blocked
54%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,726,591 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w09w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c2aa5be…d808
0x34b655…2a6f
8 touches
6 conflicts
0x01a08f7d…dec6
0x34b655…2a6f
6 touches
3 conflicts
0x5ec64628…72e4
0x34b655…2a6f
6 touches
3 conflicts
0x7fe97198…79ab
0x34b655…2a6f
6 touches
3 conflicts
0xdfbd8991…5bd1
0x34b655…2a6f
6 touches
3 conflicts
0xf4f4af3b…c5bd
0x34b655…2a6f
6 touches
3 conflicts
0x3e52c9b3…0402
0x34b655…2a6f
4 touches
1 conflict
0x427f51fd…bd80
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 0x6c2aa5be8b…b1d808
Audit this contract →
← previous block·next block →recent activity