← previous blocknext block →recent activity

Analyzing

Block #82,048,281

21 transactions · 20 stateful · 2026-06-18 07:41:48 UTC

Parallelism

52/100

Blocked

60%

Avg conflicts / tx

1.9

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #82,048,281  ·  21 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

0xf2f76ab3…623e

0x2a68ba…90c5

16 touches
28 conflicts

0x00000000…003d

0x40c49f…2af0

8 touches
6 conflicts

0x5d46e6a0…5ed9

0x40c49f…2af0

8 touches
6 conflicts

0x76d1e78d…7877

0x40c49f…2af0

6 touches
3 conflicts

0xfc578b53…9b1f

0xa6afd3…d132

4 touches
1 conflict

0xb33ff823…1188

0x065c9d…c394

4 touches
1 conflict

0x5581d709…ab77

0x2a68ba…90c5

4 touches
1 conflict

0xb3572c95…9c4a

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

28 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity