← previous blocknext block →recent activity
Analyzing
Block #87,410,025
38 transactions · 31 stateful · 2026-07-13 04:09:13 UTC
Parallelism
63/100
Blocked
77%
Avg conflicts / tx
2.5
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,410,025 · 38 txs across 14 waves · depth 14
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
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w16w210w011w113w114w115w217w418w519w620w721w822w923w1025w1126w529w231w334w635w1136w1237w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0xc514314c…1aa4
0x34b655…2a6f
14 touches
21 conflicts
0x69ce640b…884a
0x34b655…2a6f
14 touches
21 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
10 touches
10 conflicts
0x53bda555…3810
0x34b655…2a6f
10 touches
10 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
10 touches
10 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity