← previous blocknext block →recent activity
Analyzing
Block #87,499,401
37 transactions · 32 stateful · 2026-07-13 14:06:52 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
1.92
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,499,401 · 37 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w07w113w114w215w316w417w518w619w720w821w923w226w527w1033w1134w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x092832cd…7b28
0x34b655…2a6f
10 touches
10 conflicts
0x890f7ea3…b6fe
0x34b655…2a6f
10 touches
10 conflicts
0x60872583…6452
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x6b2ba712…0214
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x18e37e7d…bab2
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity