← previous blocknext block →recent activity
Analyzing
Block #87,628,737
19 transactions · 19 stateful · 2026-07-14 04:32:41 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,628,737 · 19 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
1w02w14w06w07w111w212w315w316w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x756ad195…36a3
0x34b655…2a6f
6 touches
3 conflicts
0xfc90a885…60ae
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd7fe05cd…207e
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xef1cbbb7…8cc8
0x34b655…2a6f
4 touches
1 conflict
0xfc90a885…60ad
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x756ad19507…7536a3
Audit this contract →
← previous block·next block →recent activity