← previous blocknext block →recent activity
Analyzing
Block #87,348,666
17 transactions · 16 stateful · 2026-07-12 21:18:49 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,348,666 · 17 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
1w02w13w25w06w17w28w09w210w112w313w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bc13458…e6d8
0x34b655…2a6f
6 touches
3 conflicts
0xcf504b9b…8df2
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xfcb6731c…b151
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xa4e9800f…4ab0
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 0x2bc134588d…dce6d8
Audit this contract →
← previous block·next block →recent activity