← previous blocknext block →recent activity
Analyzing
Block #88,356,560
28 transactions · 24 stateful · 2026-07-17 13:41:46 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,356,560 · 28 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
2w03w14w25w08w09w110w211w312w413w515w117w420w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x28681974…b88f
0xa6afd3…d132
6 touches
3 conflicts
0x756913cf…e7bd
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x0e525f1d…dfed
0x34b655…2a6f
4 touches
1 conflict
0x73784451…3f29
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