← previous blocknext block →recent activity

Analyzing

Block #73,033,893

37 transactions · 26 stateful · 2026-05-07 13:30:07 UTC

Parallelism

78/100

Blocked

42%

Avg conflicts / tx

0.86

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,033,893  ·  37 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x3417279f…fd02

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0002

0xd574ca…7ab1

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x17a7f697…dcb8

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x47c1a8e8…f74a

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…7212

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

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

28 conflicts on slot 0x3417279f92…37fd02

← previous block·next block →recent activity