← previous blocknext block →recent activity
Analyzing
Block #87,583,338
18 transactions · 15 stateful · 2026-07-13 23:29:04 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,583,338 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w110w111w212w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa80684c9…3948
0x34b655…2a6f
6 touches
3 conflicts
0x20ff72d4…5971
0x34b655…2a6f
6 touches
3 conflicts
0xeab8b522…d3e6
0x34b655…2a6f
6 touches
3 conflicts
0x207b4a17…4084
0x34b655…2a6f
6 touches
3 conflicts
0x4a6982a4…158c
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