← previous blocknext block →recent activity
Analyzing
Block #87,732,839
17 transactions · 17 stateful · 2026-07-14 16:08:59 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,732,839 · 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
1w02w13w26w17w010w212w213w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xa55c4598…2988
0x34b655…2a6f
6 touches
3 conflicts
0x11230290…8aa2
0x34b655…2a6f
4 touches
1 conflict
0x3726966a…669d
0x34b655…2a6f
4 touches
1 conflict
0x3cfe4586…0bd9
0x34b655…2a6f
4 touches
1 conflict
0x46e3da6b…72ca
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x67905f6e…02a1
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity