← previous blocknext block →recent activity

Analyzing

Block #83,398,796

24 transactions · 19 stateful · 2026-06-24 14:03:13 UTC

Parallelism

88/100

Blocked

32%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #83,398,796  ·  24 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

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x7a12283f…b18a

0x69df8a…6292

6 touches
3 conflicts

0x915c095e…c1e5

0x69df8a…6292

6 touches
3 conflicts

0xcfe06a18…b5b5

0x69df8a…6292

6 touches
3 conflicts

0xd8fd2add…50fc

0x69df8a…6292

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

6 touches
3 conflicts

0x1b6c23a0…723b

0x851145…3f07

6 touches
3 conflicts

0x2a628ea8…5918

0x851145…3f07

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

3 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity