← previous blocknext block →recent activity
Analyzing
Block #87,410,160
17 transactions · 17 stateful · 2026-07-13 04:10:08 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,410,160 · 17 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
5w06w17w110w212w315w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cb4b659…f735
0x34b655…2a6f
8 touches
6 conflicts
0xc8a70055…beb7
0x34b655…2a6f
4 touches
1 conflict
0x26054cbe…47df
0x34b655…2a6f
4 touches
1 conflict
0xb5c1ae56…437a
0x34b655…2a6f
4 touches
1 conflict
0x55cd0856…c7b2
0x065c9d…c394
2 touches
0 conflicts
0x6e6f4b36…ae92
0x065c9d…c394
2 touches
0 conflicts
0x095a2c84…6648
0x34b655…2a6f
2 touches
0 conflicts
0x0acd3db8…10a7
0x34b655…2a6f
2 touches
0 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 0x3cb4b65990…53f735
Audit this contract →
← previous block·next block →recent activity