← previous blocknext block →recent activity
Analyzing
Block #93,361,567
17 transactions · 14 stateful · 2026-08-05 13:41:37 UTC
Parallelism
76/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,361,567 · 17 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
1w07w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6e6f436…ddc0
0x34b655…2a6f
6 touches
3 conflicts
0x06726618…fafd
0x34b655…2a6f
4 touches
1 conflict
0x1f103e10…950e
0x34b655…2a6f
4 touches
1 conflict
0x38d4befd…1572
0x34b655…2a6f
4 touches
1 conflict
0x3d158563…8713
0x34b655…2a6f
4 touches
1 conflict
0x4560e5a8…b741
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
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 0xe6e6f4364f…80ddc0
Audit this contract →
← previous block·next block →recent activity