← previous blocknext block →recent activity
Analyzing
Block #87,749,743
17 transactions · 15 stateful · 2026-07-14 18:02:03 UTC
Parallelism
59/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,749,743 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb96a99db…95aa
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xda16e95c…521b
0x34b655…2a6f
6 touches
3 conflicts
0x9fd37234…2731
0x34b655…2a6f
6 touches
3 conflicts
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x9001f549…089d
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
6 conflicts on slot 0xb96a99db9e…4095aa
Audit this contract →
← previous block·next block →recent activity