← previous blocknext block →recent activity
Analyzing
Block #87,361,721
25 transactions · 23 stateful · 2026-07-12 22:46:06 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
1.2
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,361,721 · 25 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
1w03w05w18w09w110w211w312w113w015w116w218w319w220w221w323w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
8 touches
6 conflicts
0x2e297765…0d8b
0x34b655…2a6f
6 touches
3 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb7e6d391…2f76
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity