← previous blocknext block →recent activity
Analyzing
Block #87,733,763
25 transactions · 21 stateful · 2026-07-14 16:15:09 UTC
Parallelism
76/100
Blocked
57%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,733,763 · 25 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
1w02w13w24w05w08w09w110w211w312w413w114w316w419w522w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x0dd44476…ef40
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x5eb5d9be…b2c1
0x34b655…2a6f
6 touches
3 conflicts
0x79277877…6098
0x34b655…2a6f
6 touches
3 conflicts
0x80fd3987…2314
0x34b655…2a6f
6 touches
3 conflicts
0xbf0e051a…10a0
0x34b655…2a6f
6 touches
3 conflicts
0xbf768a2f…f453
0x34b655…2a6f
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