← previous blocknext block →recent activity
Analyzing
Block #87,737,846
17 transactions · 16 stateful · 2026-07-14 16:42:28 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,737,846 · 17 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
1w02w03w16w07w110w111w113w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c2aa5be…d808
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xac2a0273…7215
0x34b655…2a6f
4 touches
1 conflict
0xcfaa395f…5b1c
0x34b655…2a6f
4 touches
1 conflict
0xf4f4af3b…c5bd
0x34b655…2a6f
4 touches
1 conflict
0x00e76a35…df2b
0x34b655…2a6f
4 touches
1 conflict
0x0a1d16c5…fe8c
0x34b655…2a6f
4 touches
1 conflict
0x1f954224…63f8
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 0x6c2aa5be8b…b1d808
Audit this contract →
← previous block·next block →recent activity