← previous blocknext block →recent activity

Analyzing

Block #94,478,537

28 transactions · 25 stateful · 2026-08-09 11:34:39 UTC

Parallelism

82/100

Blocked

28%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,478,537  ·  28 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

0x0778475b…bd75

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x6c5f06fa…1603

0x065c9d…c394

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa2478c84…6956

0x754704…b603

4 touches
1 conflict

0x4ca422f8…936a

0x34b655…2a6f

4 touches
1 conflict

0x5502e1cc…3910

0x34b655…2a6f

4 touches
1 conflict

0x747f609d…1555

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: Kuru Exchange: MarginAccount

10 conflicts on slot 0x0778475bb2…63bd75

← previous block·next block →recent activity