← previous blocknext block →recent activity
Analyzing
Block #87,328,134
14 transactions · 12 stateful · 2026-07-12 19:01:32 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,328,134 · 14 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
5w06w17w28w09w110w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe684760e…ece0
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8653bd71…5340
0x34b655…2a6f
4 touches
1 conflict
0x95c9704c…8a57
0x34b655…2a6f
4 touches
1 conflict
0xb5436ddb…f72e
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 0xe684760e25…d1ece0
Audit this contract →
← previous block·next block →recent activity