← previous blocknext block →recent activity
Analyzing
Block #87,624,213
18 transactions · 18 stateful · 2026-07-14 04:02:23 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,624,213 · 18 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
1w03w04w17w18w29w310w011w412w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x793aa64d…b09c
0x34b655…2a6f
6 touches
3 conflicts
0x04ec4006…22b4
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x536588d3…19c5
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7138b0bd…27f1
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a4
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 0x793aa64d0d…fdb09c
Audit this contract →
← previous block·next block →recent activity