← previous blocknext block →recent activity
Analyzing
Block #93,363,543
26 transactions · 23 stateful · 2026-08-05 13:51:33 UTC
Parallelism
73/100
Blocked
35%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,363,543 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w07w18w210w012w313w414w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xa558e115…fc88
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x3661f59a…874a
0x34b655…2a6f
6 touches
3 conflicts
0xabe6698c…233b
0x34b655…2a6f
6 touches
3 conflicts
0xb1662aff…4f05
0xd32edf…ff58
5 touches
3 conflicts
0x840d3ab7…c8c4
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
10 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity