← previous blocknext block →recent activity
Analyzing
Block #87,317,976
17 transactions · 17 stateful · 2026-07-12 17:53:36 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,317,976 · 17 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
2w03w14w27w38w010w411w415w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4726587…6289
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xa05444cf…cd70
0x34b655…2a6f
6 touches
3 conflicts
0x20067ecb…0e41
0x34b655…2a6f
4 touches
1 conflict
0x6d3432e1…3642
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x75bc6537…fa92
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
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 0xd47265874d…366289
Audit this contract →
← previous block·next block →recent activity