← previous blocknext block →recent activity

Analyzing

Block #93,506,406

25 transactions · 23 stateful · 2026-08-06 01:49:47 UTC

Parallelism

80/100

Blocked

30%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,506,406  ·  25 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0x44e8f9f4…a5ad

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4bc1abab…5874

0x34b655…2a6f

4 touches
1 conflict

0x6ac4a9ce…5f63

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: USDC (USDC)

3 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity