← previous blocknext block →recent activity
Analyzing
Block #87,757,873
14 transactions · 13 stateful · 2026-07-14 18:56:24 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,757,873 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w19w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfb7adca…51d7
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x33da0dfa…bac6
0x34b655…2a6f
4 touches
1 conflict
0x36a846dc…cf4d
0x34b655…2a6f
4 touches
1 conflict
0x7a0d6712…e2a3
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xbfb7adcac2…1751d7
Audit this contract →
← previous block·next block →recent activity