← previous blocknext block →recent activity
Analyzing
Block #87,410,483
25 transactions · 23 stateful · 2026-07-13 04:12:20 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,410,483 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w27w08w110w011w212w314w015w116w217w118w119w320w422w224w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x095a2c84…6648
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x21ea036d…5d37
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
6 touches
3 conflicts
0x69ce640b…884a
0x34b655…2a6f
6 touches
3 conflicts
0x6c87ba93…686c
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x095a2c8492…716648
Audit this contract →
← previous block·next block →recent activity