← previous blocknext block →recent activity
Analyzing
Block #87,639,414
21 transactions · 16 stateful · 2026-07-14 05:44:03 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,639,414 · 21 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
4w06w07w18w212w013w114w016w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ea5ce4b…1e5b
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
6 touches
3 conflicts
0xd19c9d38…b459
0x34b655…2a6f
6 touches
3 conflicts
0xed59b1cd…8509
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x76c4d722…afaa
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x7ea5ce4bdf…4f1e5b
Audit this contract →
← previous block·next block →recent activity