← previous blocknext block →recent activity
Analyzing
Block #88,354,345
19 transactions · 17 stateful · 2026-07-17 13:26:39 UTC
Parallelism
74/100
Blocked
59%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,354,345 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w310w111w112w414w015w116w217w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf565ea1f…4245
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xdbadf6b0…43b2
0x33176b…e078
4 touches
1 conflict
0x5a3a03c4…e559
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
3 conflicts on slot 0xf565ea1f87…af4245
Audit this contract →
← previous block·next block →recent activity