← previous blocknext block →recent activity
Analyzing
Block #87,714,341
27 transactions · 23 stateful · 2026-07-14 14:05:07 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,714,341 · 27 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
6w07w19w010w112w213w014w118w119w221w322w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c11df38…2f2c
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x3d2c514e…49b1
0x34b655…2a6f
4 touches
1 conflict
0x3e6e0811…bceb
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 0x7c11df389c…6e2f2c
Audit this contract →
← previous block·next block →recent activity