← previous blocknext block →recent activity
Analyzing
Block #87,050,583
19 transactions · 17 stateful · 2026-07-11 12:05:38 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,050,583 · 19 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
1w05w17w08w110w011w113w214w215w216w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x2f358e74…1022
0x34b655…2a6f
4 touches
1 conflict
0x3c1aac7c…b2f4
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 0x94ba9c4a07…0c41d8
Audit this contract →
← previous block·next block →recent activity