← previous blocknext block →recent activity

Analyzing

Block #93,151,180

21 transactions · 20 stateful · 2026-08-04 20:03:49 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,151,180  ·  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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd9f1e40f…09a3

0x3bd359…433a

10 touches
10 conflicts

0x527f20e3…82e7

0x754704…b603

10 touches
10 conflicts

0xc33671eb…4466

0x34b655…2a6f

4 touches
1 conflict

0x033cf007…136d

0x34b655…2a6f

4 touches
1 conflict

0x96c36734…b2e3

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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: Wrapped MON (WMON)

10 conflicts on slot 0xd9f1e40f03…3209a3

← previous block·next block →recent activity