← previous blocknext block →recent activity
Analyzing
Block #87,579,010
33 transactions · 21 stateful · 2026-07-13 23:00:06 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,579,010 · 33 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
4w08w013w114w215w316w017w118w121w023w124w231w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
6 touches
3 conflicts
0xab125595…d715
0x40c49f…2af0
5 touches
3 conflicts
0x1b5f5a50…c006
0x34b655…2a6f
4 touches
1 conflict
0x20134ee4…87a3
0x34b655…2a6f
4 touches
1 conflict
0x2a88784d…f1be
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 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity