← previous blocknext block →recent activity
Analyzing
Block #87,711,519
19 transactions · 16 stateful · 2026-07-14 13:46:11 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,711,519 · 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
5w07w18w210w011w313w314w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa38eb2fc…1658
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7fa1794c…3323
0x34b655…2a6f
4 touches
1 conflict
0xa505051b…0632
0x34b655…2a6f
4 touches
1 conflict
0xa646ab9d…f468
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 0xa38eb2fcd4…781658
Audit this contract →
← previous block·next block →recent activity