← previous blocknext block →recent activity
Analyzing
Block #87,712,928
22 transactions · 19 stateful · 2026-07-14 13:55:37 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.41
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,712,928 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w38w49w516w621w6
- 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
14 touches
21 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x67905f6e…02a1
0x34b655…2a6f
12 touches
15 conflicts
0xb39e680b…ee85
0x34b655…2a6f
10 touches
10 conflicts
0x34d95d94…3a16
0x34b655…2a6f
10 touches
10 conflicts
0x875164c2…f8a2
0x34b655…2a6f
9 touches
10 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