← previous blocknext block →recent activity
Analyzing
Block #87,722,532
23 transactions · 20 stateful · 2026-07-14 15:00:00 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,722,532 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w08w19w010w112w013w215w216w119w020w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50718952…7c75
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7f3ca729…0c7d
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7f2db611…3990
0x34b655…2a6f
4 touches
1 conflict
0x8655fbf5…916c
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 0x507189525d…837c75
Audit this contract →
← previous block·next block →recent activity