← previous blocknext block →recent activity
Analyzing
Block #87,409,144
57 transactions · 51 stateful · 2026-07-13 04:03:19 UTC
Parallelism
67/100
Blocked
73%
Avg conflicts / tx
3.16
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,409,144 · 57 txs across 19 waves · depth 19
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
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w09w211w312w413w014w138w441w542w643w755w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0xc514314c…1aa4
0x34b655…2a6f
22 touches
55 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
18 touches
36 conflicts
0x9ef9caab…9c45
0x34b655…2a6f
16 touches
28 conflicts
0x5690b0e1…17e4
0x34b655…2a6f
16 touches
28 conflicts
0xc03846bb…73b3
0x34b655…2a6f
16 touches
28 conflicts
0xe9f7d7ae…6c07
0x34b655…2a6f
16 touches
28 conflicts
0x806de663…2ff1
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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity