← previous blocknext block →recent activity

Analyzing

Block #84,543,181

19 transactions · 17 stateful · 2026-06-29 21:13:51 UTC

Parallelism

79/100

Blocked

41%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,543,181  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x148e5f26…b292

0xa6afd3…d132

4 touches
1 conflict

0xf412c531…d397

0xa6afd3…d132

4 touches
1 conflict

0x92339d95…0800

0x0000a8…8888

4 touches
1 conflict

0xa9db7b4d…2957

0x40c49f…2af0

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

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