← previous blocknext block →recent activity
Analyzing
Block #87,620,842
16 transactions · 13 stateful · 2026-07-14 03:39:50 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,620,842 · 16 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
1w06w07w18w19w210w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 conflicts
0x7947ecc3…dde4
0x34b655…2a6f
5 touches
3 conflicts
0x0f15f74f…8d71
0x34b655…2a6f
4 touches
1 conflict
0x1636bc9b…fe16
0x34b655…2a6f
4 touches
1 conflict
0x2da89dae…f0b7
0x34b655…2a6f
4 touches
1 conflict
0x41fc2b04…2805
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x79ace5b6…8d37
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 0x7e5ea60ab2…b0c4a4
Audit this contract →
← previous block·next block →recent activity