← previous blocknext block →recent activity
Analyzing
Block #87,726,601
25 transactions · 23 stateful · 2026-07-14 15:27:14 UTC
Parallelism
56/100
Blocked
65%
Avg conflicts / tx
2.96
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,726,601 · 25 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w28w39w410w511w612w713w814w924w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c2aa5be…d808
0x34b655…2a6f
22 touches
55 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x5170a218…3a84
0xc8689a…ee79
16 touches
28 conflicts
0x63c900f4…2600
0x34b655…2a6f
16 touches
28 conflicts
0xad0c7701…1d83
0x34b655…2a6f
16 touches
28 conflicts
0xe1314260…117d
0x34b655…2a6f
16 touches
28 conflicts
0x01a08f7d…dec6
0x34b655…2a6f
16 touches
28 conflicts
0x5ec64628…72e4
0x34b655…2a6f
14 touches
21 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
55 conflicts on slot 0x6c2aa5be8b…b1d808
Audit this contract →
← previous block·next block →recent activity