← previous blocknext block →recent activity
Analyzing
Block #87,669,383
16 transactions · 13 stateful · 2026-07-14 09:04:14 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,669,383 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w08w19w210w311w412w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x43076802…d920
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x4e6eebc7…a18c
0x34b655…2a6f
4 touches
1 conflict
0x859fe39d…effa
0x34b655…2a6f
4 touches
1 conflict
0x8d918dce…e66d
0x34b655…2a6f
4 touches
1 conflict
0x9a29b949…58de
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity