← previous blocknext block →recent activity
Analyzing
Block #87,707,510
25 transactions · 20 stateful · 2026-07-14 13:19:21 UTC
Parallelism
84/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,707,510 · 25 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
1w02w03w14w05w18w09w010w011w112w113w214w216w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0f556856…2916
0x34b655…2a6f
6 touches
3 conflicts
0xdf15e2bf…d7a9
0x34b655…2a6f
6 touches
3 conflicts
0x0f8965bb…e238
0x34b655…2a6f
4 touches
1 conflict
0x1febc2d0…0136
0x34b655…2a6f
4 touches
1 conflict
0x20067ecb…0e41
0x34b655…2a6f
4 touches
1 conflict
0x2afe51f4…4006
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity