← previous blocknext block →recent activity

Analyzing

Block #94,971,651

28 transactions · 19 stateful · 2026-08-11 04:56:23 UTC

Parallelism

71/100

Blocked

68%

Avg conflicts / tx

1.18

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,971,651  ·  28 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x11258774…9892

0x2a68ba…90c5

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0xb33ff823…1188

0x065c9d…c394

8 touches
6 conflicts

0x46d0384e…ad55

0x065c9d…c394

7 touches
6 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

6 touches
3 conflicts

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

15 conflicts on slot 0x1125877469…519892

← previous block·next block →recent activity