← previous blocknext block →recent activity

Analyzing

Block #72,978,135

41 transactions · 30 stateful · 2026-05-07 07:19:01 UTC

Parallelism

71/100

Blocked

70%

Avg conflicts / tx

1.9

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #72,978,135  ·  41 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x17606ba6…1b6e

0x754704…b603

14 touches
21 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x8aa1941d…2988

0x34b655…2a6f

10 touches
10 conflicts

0x2c7e5699…a792

0x34b655…2a6f

8 touches
6 conflicts

0x3c35979a…975d

0x34b655…2a6f

8 touches
6 conflicts

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: 0x754704bc…afb603

21 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity