← previous blocknext block →recent activity

Analyzing

Block #94,741,848

16 transactions · 14 stateful · 2026-08-10 09:39:40 UTC

Parallelism

81/100

Blocked

50%

Avg conflicts / tx

0.63

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,741,848  ·  16 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

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x93b6fab0…09d6

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xe2e52e46…0894

0x34b655…2a6f

4 touches
1 conflict

0xe8d58d34…426d

0x34b655…2a6f

4 touches
1 conflict

0xf3383813…4a0c

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

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

3 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity