← previous blocknext block →recent activity
Analyzing
Block #87,691,694
19 transactions · 19 stateful · 2026-07-14 11:33:21 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,691,694 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w010w111w212w316w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf68b5d2…0eba
0x34b655…2a6f
10 touches
10 conflicts
0x4f51d069…d0b4
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xed59b1cd…8509
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x49f75237…44f4
0x34b655…2a6f
10 touches
10 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
8 touches
6 conflicts
0x6893debf…ca65
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
10 conflicts on slot 0xbf68b5d236…8c0eba
Audit this contract →
← previous block·next block →recent activity