← previous blocknext block →recent activity
Analyzing
Block #87,346,387
20 transactions · 17 stateful · 2026-07-12 21:03:34 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,346,387 · 20 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
1w02w16w07w18w210w112w013w114w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f461725…5ab2
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x390b9800…1635
0x34b655…2a6f
4 touches
1 conflict
0x3ef0952c…762d
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x78255c70…2733
0x34b655…2a6f
4 touches
1 conflict
0x78255c70…2734
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 0x2f4617255d…ea5ab2
Audit this contract →
← previous block·next block →recent activity