← previous blocknext block →recent activity
Analyzing
Block #87,726,548
15 transactions · 14 stateful · 2026-07-14 15:26:53 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,726,548 · 15 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
1w02w03w14w25w110w213w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x6c2aa5be…d808
0x34b655…2a6f
6 touches
3 conflicts
0x5e5ce24b…6023
0x34b655…2a6f
4 touches
1 conflict
0x5ec64628…72e4
0x34b655…2a6f
4 touches
1 conflict
0x8a705be8…7ac4
0xc8689a…ee79
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x388633a0…86cd
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity