← previous blocknext block →recent activity
Analyzing
Block #87,050,113
10 transactions · 9 stateful · 2026-07-11 12:02:30 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,050,113 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb88134d…d6c1
0x34b655…2a6f
6 touches
3 conflicts
0xdb88134d…d6c2
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x363a4317…87d2
0x34b655…2a6f
4 touches
1 conflict
0x36783e42…97d1
0x34b655…2a6f
4 touches
1 conflict
0x38948e75…437a
0x34b655…2a6f
4 touches
1 conflict
0x4f0e96a2…6708
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 0xdb88134d85…15d6c1
Audit this contract →
← previous block·next block →recent activity