← previous blocknext block →recent activity
Analyzing
Block #88,137,937
21 transactions · 19 stateful · 2026-07-16 13:18:36 UTC
Parallelism
67/100
Blocked
37%
Avg conflicts / tx
0.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,137,937 · 21 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
1w07w08w110w211w312w414w515w120w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25ff7717…d4af
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x9b68408a…e609
0x34b655…2a6f
4 touches
1 conflict
0x9c2493d7…ab9c
0x34b655…2a6f
4 touches
1 conflict
0x9c2493d7…ab9d
0x34b655…2a6f
4 touches
1 conflict
0x9c3004b2…5421
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
10 conflicts on slot 0x25ff77178c…2ad4af
Audit this contract →
← previous block·next block →recent activity