← previous blocknext block →recent activity

Analyzing

Block #94,469,315

19 transactions · 19 stateful · 2026-08-09 10:48:13 UTC

Parallelism

84/100

Blocked

32%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,469,315  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x724cd9ff…6684

0x0cc9b2…7777

6 touches
3 conflicts

0x00000000…0008

0x0ea966…0742

6 touches
3 conflicts

0x44ad89ba…cf83

0xe4f6e7…9657

6 touches
3 conflicts

0x724cd9ff…6684

0xe4f6e7…9657

6 touches
3 conflicts

0x1d0a04dd…b892

0x34b655…2a6f

4 touches
1 conflict

0x1dd015c2…edf4

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

3 conflicts on slot 0x724cd9ff19…4c6684

← previous block·next block →recent activity