← previous blocknext block →recent activity
Analyzing
Block #87,513,533
14 transactions · 14 stateful · 2026-07-13 15:41:29 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,513,533 · 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
2w04w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x295faadc…ed75
0x34b655…2a6f
4 touches
1 conflict
0x2b4f426d…5de5
0x34b655…2a6f
4 touches
1 conflict
0x34731dbd…e467
0x34b655…2a6f
4 touches
1 conflict
0x35feab12…a169
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7b
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity