← previous blocknext block →recent activity

Analyzing

Block #84,573,150

17 transactions · 14 stateful · 2026-06-30 00:33:59 UTC

Parallelism

71/100

Blocked

57%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,573,150  ·  17 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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x0c969dde…6b06

0xa6afd3…d132

6 touches
3 conflicts

0x29686688…0598

0xa6afd3…d132

6 touches
3 conflicts

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x56785e37…a197

0x065c9d…c394

4 touches
1 conflict

0xb3572c95…9c4a

0x2a68ba…90c5

4 touches
1 conflict

0x37d5916a…e60c

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

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity