← previous blocknext block →recent activity

Analyzing

Block #94,200,037

19 transactions · 17 stateful · 2026-08-08 12:01:16 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,200,037  ·  19 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

0x4cabb80a…46bf

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x6dc9ce26…f4f4

0x065c9d…c394

4 touches
1 conflict

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0x0221091a…da2a

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

10 conflicts on slot 0x4cabb80a0e…7546bf

← previous block·next block →recent activity