← previous blocknext block →recent activity

Analyzing

Block #94,914,764

21 transactions · 19 stateful · 2026-08-11 00:10:16 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #94,914,764  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0x11b69a7e…334e

0x01bff4…1071

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x00ddbbf2…4588

0x34b655…2a6f

4 touches
1 conflict

0x6d5492bb…23eb

0x851145…3f07

4 touches
1 conflict

0xf13704e6…258a

0x01bff4…1071

4 touches
1 conflict

0x062c1596…769e

0x065c9d…c394

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)

15 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity