← previous blocknext block →recent activity

Analyzing

Block #79,418,388

28 transactions · 22 stateful · 2026-06-06 03:19:05 UTC

Parallelism

64/100

Blocked

64%

Avg conflicts / tx

1.86

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #79,418,388  ·  28 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x13a54fa2…5ae3

0x2a68ba…90c5

16 touches
28 conflicts

0x00000000…003d

0xa6afd3…d132

16 touches
28 conflicts

0x5da4ed2f…283f

0xa6afd3…d132

14 touches
21 conflicts

0xc05b880b…7746

0xa6afd3…d132

14 touches
21 conflicts

0x40970e69…da50

0x69df8a…6292

12 touches
15 conflicts

0xb05cd4f5…73d0

0x69df8a…6292

12 touches
15 conflicts

0xdb067026…9eb8

0x69df8a…6292

12 touches
15 conflicts

0xdf708ee7…1fcf

0xc8689a…ee79

12 touches
15 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

28 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity