← previous blocknext block →recent activity

Analyzing

Block #73,043,210

33 transactions · 29 stateful · 2026-05-07 14:32:07 UTC

Parallelism

64/100

Blocked

66%

Avg conflicts / tx

2.64

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,043,210  ·  33 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

0x00000000…0002

0xab3526…fa38

24 touches
66 conflicts

0xdb907629…39aa

0x34b655…2a6f

12 touches
15 conflicts

0x388e001a…7e04

0x34b655…2a6f

12 touches
15 conflicts

0xaa3492db…3703

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

10 touches
10 conflicts

0x9cc607d0…c9c7

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 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: 0xab35264b…1cfa38

66 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity