← previous blocknext block →recent activity
Analyzing
Block #87,410,617
18 transactions · 18 stateful · 2026-07-13 04:13:14 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,410,617 · 18 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
2w03w15w17w212w013w115w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x7c46fde6…d6a0
0x34b655…2a6f
6 touches
3 conflicts
0x6ccf5c86…9954
0x851145…3f07
4 touches
1 conflict
0x1ae5d5a7…0da2
0x2a68ba…90c5
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8fe37a3f…4c89
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
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 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity