← previous blocknext block →recent activity

Analyzing

Block #94,486,203

18 transactions · 16 stateful · 2026-08-09 12:13:12 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.89

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,486,203  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x95c47f03…f1bb

0x34b655…2a6f

8 touches
6 conflicts

0x8f2a0c48…753c

0x065c9d…c394

6 touches
3 conflicts

0x0778475b…bd75

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x93b6fab0…09d6

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xbd97c3fe…85d3

0x34b655…2a6f

4 touches
1 conflict

0xf094e5be…d695

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

6 conflicts on slot 0x95c47f0322…51f1bb

← previous block·next block →recent activity