← previous blocknext block →recent activity
Analyzing
Block #87,284,306
17 transactions · 16 stateful · 2026-07-12 14:08:30 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,284,306 · 17 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
1w02w13w04w15w210w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x3e8b3a49…53ee
0x34b655…2a6f
6 touches
3 conflicts
0x875c3459…2879
0x34b655…2a6f
6 touches
3 conflicts
0x4982e9a7…d274
0x699abc…6a3b
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0xba54c30f…7bfd
0x065c9d…c394
4 touches
1 conflict
0x92d610a6…9a40
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity