← previous blocknext block →recent activity
Analyzing
Block #87,733,376
16 transactions · 15 stateful · 2026-07-14 16:12:34 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,733,376 · 16 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
1w02w13w04w15w06w17w210w111w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x067c61b8…650f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xe8377f79…5f5e
0x34b655…2a6f
4 touches
1 conflict
0xff1c6931…7633
0x34b655…2a6f
4 touches
1 conflict
0x085c9fac…8fcf
0x8d1565…6723
4 touches
1 conflict
0x10a2bd5d…ad6d
0x8d1565…6723
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 0x067c61b803…d7650f
Audit this contract →
← previous block·next block →recent activity