← previous blocknext block →recent activity
Analyzing
Block #87,576,139
23 transactions · 21 stateful · 2026-07-13 22:40:54 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,576,139 · 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
2w03w05w16w28w09w110w213w015w116w317w418w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
6 touches
3 conflicts
0x2e0719b8…70a7
0x34b655…2a6f
6 touches
3 conflicts
0x44fdb4b6…2ce4
0x34b655…2a6f
6 touches
3 conflicts
0x44fdb4b6…2ce5
0x34b655…2a6f
6 touches
3 conflicts
0x4dd19eaa…75bd
0x34b655…2a6f
6 touches
3 conflicts
0x5e17e5be…d212
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 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity