← previous blocknext block →recent activity
Analyzing
Block #87,623,317
14 transactions · 13 stateful · 2026-07-14 03:56:23 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,623,317 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w08w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x4a5956ef…e226
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x20fbcaee…bb79
0x34b655…2a6f
6 touches
3 conflicts
0x9407f89d…82ff
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity