← previous blocknext block →recent activity
Analyzing
Block #87,133,412
10 transactions · 9 stateful · 2026-07-11 21:18:46 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,133,412 · 10 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
1w02w03w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21082490…de66
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x266a6b2c…4377
0x34b655…2a6f
4 touches
1 conflict
0x3bffe642…cff3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6a2ebbdd…0438
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 0x2108249028…bfde66
Audit this contract →
← previous block·next block →recent activity