← previous blocknext block →recent activity
Analyzing
Block #87,753,586
17 transactions · 16 stateful · 2026-07-14 18:27:45 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,753,586 · 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
1w02w15w06w17w28w39w410w512w113w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x366f651e…6100
0x34b655…2a6f
6 touches
3 conflicts
0x388633a0…86cd
0x34b655…2a6f
6 touches
3 conflicts
0x70b90757…51be
0x34b655…2a6f
6 touches
3 conflicts
0xc2186704…5cc3
0x34b655…2a6f
6 touches
3 conflicts
0x59dccbd8…2bf6
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