← previous blocknext block →recent activity
Analyzing
Block #87,623,969
24 transactions · 21 stateful · 2026-07-14 04:00:45 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,623,969 · 24 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
3w04w16w17w28w39w410w513w016w122w223w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb7c435f…f490
0x34b655…2a6f
14 touches
21 conflicts
0x18e900fa…07f4
0x34b655…2a6f
10 touches
10 conflicts
0x1ee4a6d2…6389
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x25329a48…4e00
0x34b655…2a6f
10 touches
10 conflicts
0x297e36f3…9800
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0xcef0e4b7…46bf
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xdb7c435f8d…b5f490
Audit this contract →
← previous block·next block →recent activity