← previous blocknext block →recent activity
Analyzing
Block #87,730,456
24 transactions · 23 stateful · 2026-07-14 15:53:02 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,730,456 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w210w312w113w214w318w419w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c9704c…8a57
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xc4de6652…13f4
0x34b655…2a6f
6 touches
3 conflicts
0x5a310d83…cae0
0x34b655…2a6f
6 touches
3 conflicts
0x87d20e73…1071
0x34b655…2a6f
6 touches
3 conflicts
0x95c2cdec…c059
0x34b655…2a6f
4 touches
1 conflict
0x99bc8b1a…2c66
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
10 conflicts on slot 0x95c9704c08…fd8a57
Audit this contract →
← previous block·next block →recent activity