← previous blocknext block →recent activity
Analyzing
Block #87,623,271
24 transactions · 24 stateful · 2026-07-14 03:56:05 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,623,271 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w19w010w011w112w213w214w315w418w522w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xe8352ac7…d7a3
0x34b655…2a6f
8 touches
6 conflicts
0xd026fe03…7748
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x8e507257…71c1
0x34b655…2a6f
6 touches
3 conflicts
0xcb3b5e8c…053a
0x34b655…2a6f
6 touches
3 conflicts
0xd379a368…fea4
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
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