← previous blocknext block →recent activity
Analyzing
Block #87,735,398
27 transactions · 23 stateful · 2026-07-14 16:26:05 UTC
Parallelism
81/100
Blocked
30%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,735,398 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w111w012w115w016w117w123w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x25bdc7e4…b92e
0x34b655…2a6f
4 touches
1 conflict
0x323fde37…d7bb
0x34b655…2a6f
4 touches
1 conflict
0x323fde37…d7bc
0x34b655…2a6f
4 touches
1 conflict
0x3cfe4586…0bd9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b297152…4446
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 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity