← previous blocknext block →recent activity
Analyzing
Block #87,730,468
17 transactions · 14 stateful · 2026-07-14 15:53:06 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,730,468 · 17 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
2w03w14w25w36w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
4 touches
1 conflict
0xc4de6652…13f4
0x34b655…2a6f
4 touches
1 conflict
0xdc57039b…df61
0x34b655…2a6f
4 touches
1 conflict
0xeeaba9d3…b491
0x34b655…2a6f
4 touches
1 conflict
0x5170a218…3a84
0xc8689a…ee79
4 touches
1 conflict
0x0ba865dd…a249
0x34b655…2a6f
4 touches
1 conflict
0x22e7ebfe…1293
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity