← previous blocknext block →recent activity

Analyzing

Block #73,043,090

37 transactions · 27 stateful · 2026-05-07 14:31:19 UTC

Parallelism

76/100

Blocked

59%

Avg conflicts / tx

1.51

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,043,090  ·  37 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x88230a4f…8a7c

0xd32edf…ff58

13 touches
21 conflicts

0x388e001a…7e04

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xdb907629…39aa

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xba5743c7…21c6

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x0b28bf77…e53a

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

21 conflicts on slot 0x88230a4f3b…1a8a7c

← previous block·next block →recent activity