← previous blocknext block →recent activity

Analyzing

Block #73,338,541

22 transactions · 18 stateful · 2026-05-08 23:17:00 UTC

Parallelism

50/100

Blocked

67%

Avg conflicts / tx

2.64

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,338,541  ·  22 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x81bbe254…c60c

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x46cb45de…a567

0x188d58…ea8e

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xc1baef71…068c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x46cb45de…a566

0x188d58…ea8e

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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: 0xd32edf66…9fff58

55 conflicts on slot 0x81bbe25435…4fc60c

← previous block·next block →recent activity