← previous blocknext block →recent activity
Analyzing
Block #87,594,675
16 transactions · 13 stateful · 2026-07-14 00:44:53 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,594,675 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2df6f59b…d662
0x34b655…2a6f
4 touches
1 conflict
0x5f57e7ab…9f8d
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0xc8155427…d542
0x34b655…2a6f
4 touches
1 conflict
0x0a5dbc1e…74cc
0x34b655…2a6f
2 touches
0 conflicts
0x12a92ce8…db54
0x34b655…2a6f
2 touches
0 conflicts
0x176771f9…c1a4
0x34b655…2a6f
2 touches
0 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x2df6f59b44…a3d662
Audit this contract →
← previous block·next block →recent activity