← previous blocknext block →recent activity

Analyzing

Block #94,490,906

17 transactions · 17 stateful · 2026-08-09 12:36:52 UTC

Parallelism

82/100

Blocked

35%

Avg conflicts / tx

0.53

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,490,906  ·  17 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

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x0778475b…bd75

0x2a68ba…90c5

6 touches
3 conflicts

0xd98fbb19…4fae

0x065c9d…c394

5 touches
3 conflicts

0x2dd03fb9…6243

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0x70eec2ed…f791

0x34b655…2a6f

4 touches
1 conflict

0x74f95963…01a2

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0xbde524f475…b143bf

← previous block·next block →recent activity