← previous blocknext block →recent activity

Analyzing

Block #81,013,867

19 transactions · 15 stateful · 2026-06-13 12:48:30 UTC

Parallelism

74/100

Blocked

53%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #81,013,867  ·  19 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

0x00000000…003d

0x40c49f…2af0

8 touches
6 conflicts

0x76d1e78d…7877

0x40c49f…2af0

6 touches
3 conflicts

0x5d46e6a0…5ed9

0x40c49f…2af0

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x90f07a4f…d932

0x34b655…2a6f

4 touches
1 conflict

0xac3e4969…39e9

0x34b655…2a6f

4 touches
1 conflict

0xd1a8b9bd…6f8c

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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: 0x40c49f17…d22af0

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity