← previous blocknext block →recent activity
Analyzing
Block #87,351,125
14 transactions · 14 stateful · 2026-07-12 21:35:15 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,351,125 · 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
3w07w08w19w210w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd6e61f7…3ede
0x34b655…2a6f
6 touches
3 conflicts
0x216ffe66…1f94
0x34b655…2a6f
6 touches
3 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x1fa0a23d…12b6
0x34b655…2a6f
4 touches
1 conflict
0xb96a99db…95aa
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 0xbd6e61f76f…523ede
Audit this contract →
← previous block·next block →recent activity