← previous blocknext block →recent activity
Analyzing
Block #87,706,323
17 transactions · 15 stateful · 2026-07-14 13:11:25 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,706,323 · 17 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
2w03w14w210w111w313w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa1bfcc4c…f2db
0x851145…3f07
4 touches
1 conflict
0xc2e36a04…b85e
0x851145…3f07
4 touches
1 conflict
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0x452a3ead…122a
0x40c49f…2af0
4 touches
1 conflict
0xa256367b…2268
0x40c49f…2af0
4 touches
1 conflict
0xca1a599d…a6da
0x40c49f…2af0
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: 0x40c49f17…d22af0
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity