← previous blocknext block →recent activity
Analyzing
Block #87,757,663
31 transactions · 28 stateful · 2026-07-14 18:55:00 UTC
Parallelism
81/100
Blocked
61%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,757,663 · 31 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
1w02w14w25w36w07w18w09w110w011w112w213w314w419w122w423w427w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
8 touches
6 conflicts
0xa4f80979…4d71
0x065c9d…c394
8 touches
6 conflicts
0xd35bb5ac…3586
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xd5b10148…e637
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity