← previous blocknext block →recent activity
Analyzing
Block #87,488,913
13 transactions · 11 stateful · 2026-07-13 12:56:40 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,488,913 · 13 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x57c8db9d…3979
0x34b655…2a6f
4 touches
1 conflict
0x3a5224d1…ee57
0x34b655…2a6f
4 touches
1 conflict
0x633cec1c…ab06
0x34b655…2a6f
4 touches
1 conflict
0x82ac3a8f…c105
0x34b655…2a6f
4 touches
1 conflict
0x9c1e34a2…a218
0x34b655…2a6f
4 touches
1 conflict
0x17e46624…6145
0x34b655…2a6f
2 touches
0 conflicts
0x1e212d2d…8ac8
0x34b655…2a6f
2 touches
0 conflicts
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity