← previous blocknext block →recent activity
Analyzing
Block #93,576,511
21 transactions · 20 stateful · 2026-08-06 07:42:12 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,576,511 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w27w08w19w210w012w114w317w220w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xca0d00ce…5b43
0x34b655…2a6f
6 touches
3 conflicts
0x426953d0…f1a3
0xd32edf…ff58
5 touches
3 conflicts
0x20d79862…96f0
0x34b655…2a6f
4 touches
1 conflict
0x21ab01d0…c3c3
0x34b655…2a6f
4 touches
1 conflict
0x2a3484ea…8054
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity