← previous blocknext block →recent activity
Analyzing
Block #87,713,071
23 transactions · 20 stateful · 2026-07-14 13:56:34 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,713,071 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w410w513w117w218w621w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xa6389d47…9a28
0x34b655…2a6f
12 touches
15 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
10 touches
10 conflicts
0xd11dcf4e…518f
0x34b655…2a6f
10 touches
10 conflicts
0xfa551be3…a911
0xa6afd3…d132
6 touches
3 conflicts
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity