← previous blocknext block →recent activity
Analyzing
Block #87,330,265
19 transactions · 19 stateful · 2026-07-12 19:15:48 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,330,265 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w28w09w110w011w212w315w216w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6ed530c…d450
0x34b655…2a6f
8 touches
6 conflicts
0x680ca7d7…2df4
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x9216894f…5d86
0x34b655…2a6f
4 touches
1 conflict
0xde4210b8…8fa9
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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
6 conflicts on slot 0xb6ed530c56…eed450
Audit this contract →
← previous block·next block →recent activity