← previous blocknext block →recent activity
Analyzing
Block #87,785,347
28 transactions · 21 stateful · 2026-07-14 22:00:15 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,785,347 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w115w016w118w219w120w322w223w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0x154f65cf…14d6
0x34b655…2a6f
4 touches
1 conflict
0x1f954224…63f8
0x34b655…2a6f
4 touches
1 conflict
0x1f954224…63f9
0x34b655…2a6f
4 touches
1 conflict
0x220a8541…6431
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity