← previous blocknext block →recent activity
Analyzing
Block #87,421,382
30 transactions · 22 stateful · 2026-07-13 05:25:12 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,421,382 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w111w012w013w115w116w219w321w422w523w124w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76196ad0…ce0c
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0xfffe583a…9130
0x34b655…2a6f
6 touches
3 conflicts
0xad95efd9…b4cf
0x34b655…2a6f
6 touches
3 conflicts
0x3c7908ed…47c8
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
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
10 conflicts on slot 0x76196ad0db…ffce0c
Audit this contract →
← previous block·next block →recent activity