← previous blocknext block →recent activity
Analyzing
Block #87,624,910
20 transactions · 19 stateful · 2026-07-14 04:07:03 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,624,910 · 20 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
1w04w05w111w012w113w114w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xfc4d32c0…39f9
0x34b655…2a6f
4 touches
1 conflict
0xcda8dd4d…0606
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0001
0xc1ff9f…b0fc
4 touches
1 conflict
0x7ff11cc0…fed4
0x40c49f…2af0
4 touches
1 conflict
0x39844261…0e6f
0x40c49f…2af0
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: 0x40c49f17…d22af0
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity