← previous blocknext block →recent activity

Analyzing

Block #73,338,535

35 transactions · 24 stateful · 2026-05-08 23:16:57 UTC

Parallelism

51/100

Blocked

71%

Avg conflicts / tx

3.91

Longest chain

17 deep

Execution timeline

did this block parallelize well?

view

block #73,338,535  ·  35 txs across 17 waves  ·  depth 17
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

wave w12

wave w13

wave w14

wave w15

wave w16

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

0xcea2d697…3820

0xd32edf…ff58

33 touches
136 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0x21d8e673…067e

0x1b6862…e19c

4 touches
1 conflict

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

136 conflicts on slot 0xcea2d6970b…093820

← previous block·next block →recent activity