← previous blocknext block →recent activity
Analyzing
Block #87,316,023
17 transactions · 16 stateful · 2026-07-12 17:40:32 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,316,023 · 17 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
1w02w13w28w09w110w211w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4e5e0c2…6e04
0x34b655…2a6f
6 touches
3 conflicts
0x680ca7d7…2df4
0x34b655…2a6f
6 touches
3 conflicts
0xc2f33b67…92d0
0xd32edf…ff58
5 touches
3 conflicts
0x1f6b228e…f0a0
0x34b655…2a6f
4 touches
1 conflict
0x38390c5d…d455
0x34b655…2a6f
4 touches
1 conflict
0x42aad825…b067
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a4
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 0xa4e5e0c2c4…d76e04
Audit this contract →
← previous block·next block →recent activity