← previous blocknext block →recent activity

Analyzing

Block #81,480,465

20 transactions · 17 stateful · 2026-06-15 16:36:20 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #81,480,465  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x2c492d…444e

6 touches
3 conflicts

0x44ad89ba…cf83

0x5df178…7777

6 touches
3 conflicts

0x73131ffc…b46c

0x5df178…7777

6 touches
3 conflicts

0x00000000…0001

0x2c492d…444e

6 touches
3 conflicts

0xc740dd24…9801

0x3bd359…433a

6 touches
3 conflicts

0xa7013be2…c0a8

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