← previous blocknext block →recent activity

Analyzing

Block #108,549,594

30 transactions · 22 stateful · 2026-09-27 19:32:57 UTC

Parallelism

80/100

Blocked

36%

Avg conflicts / tx

0.53

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #108,549,594  ·  30 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x3d4e97b5…00b7

0x34b655…2a6f

4 touches
1 conflict

0x54e6d2a8…ec22

0x34b655…2a6f

4 touches
1 conflict

0x58c1b78b…ef3f

0x34b655…2a6f

4 touches
1 conflict

0x7bd229ad…63b2

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 0xf2f76ab392…f3623e

← previous block·next block →recent activity