← previous blocknext block →recent activity
Analyzing
Block #87,669,433
13 transactions · 12 stateful · 2026-07-14 09:04:35 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,669,433 · 13 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
2w03w15w06w17w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc909c435…3dab
0x34b655…2a6f
6 touches
3 conflicts
0x0e22f39d…b92b
0x34b655…2a6f
4 touches
1 conflict
0x43bc2389…898f
0x34b655…2a6f
4 touches
1 conflict
0x4982229d…6f85
0x34b655…2a6f
4 touches
1 conflict
0x56f7a389…74fd
0x34b655…2a6f
4 touches
1 conflict
0x61757a59…d89f
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity