← previous blocknext block →recent activity
Analyzing
Block #87,584,712
14 transactions · 11 stateful · 2026-07-13 23:38:15 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,584,712 · 14 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
1w02w13w26w07w28w19w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f8a50d…333b
0x34b655…2a6f
6 touches
3 conflicts
0x18904470…0ef9
0x34b655…2a6f
6 touches
3 conflicts
0x17cc5ec3…ae0e
0x34b655…2a6f
4 touches
1 conflict
0x2447fab0…811d
0x34b655…2a6f
4 touches
1 conflict
0x34425c26…0709
0x34b655…2a6f
4 touches
1 conflict
0x3ea25e92…a36d
0x34b655…2a6f
4 touches
1 conflict
0x4a559be0…1f90
0x34b655…2a6f
4 touches
1 conflict
0x5d2f0b01…112a
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 0x63f8a50db5…53333b
Audit this contract →
← previous block·next block →recent activity