← previous blocknext block →recent activity

Analyzing

Block #81,449,208

23 transactions · 17 stateful · 2026-06-15 13:07:58 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #81,449,208  ·  23 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x2c6739b3…f7dc

0x34b655…2a6f

6 touches
3 conflicts

0xd7bf6947…0c7d

0x34b655…2a6f

6 touches
3 conflicts

0x6e5daa4e…8230

0x34b655…2a6f

6 touches
3 conflicts

0x9f287382…28e5

0x34b655…2a6f

6 touches
3 conflicts

0xa19aba84…8922

0xa6afd3…d132

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x6c512890…c994

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: Perpl

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity