← previous blocknext block →recent activity
Analyzing
Block #87,665,475
25 transactions · 19 stateful · 2026-07-14 08:38:09 UTC
Parallelism
84/100
Blocked
26%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,665,475 · 25 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
5w07w08w19w011w114w116w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x4ab0fef9…caef
0x34b655…2a6f
4 touches
1 conflict
0x8f825eeb…9942
0x851145…3f07
4 touches
1 conflict
0xd3406c63…f416
0x851145…3f07
4 touches
1 conflict
0xbbae5d58…a956
0x34b655…2a6f
4 touches
1 conflict
0x010bab9f…6b7e
0x851145…3f07
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…b0c4aa
Audit this contract →
← previous block·next block →recent activity