← previous blocknext block →recent activity

Analyzing

Block #73,043,202

27 transactions · 20 stateful · 2026-05-07 14:32:04 UTC

Parallelism

70/100

Blocked

45%

Avg conflicts / tx

1.04

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,043,202  ·  27 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

0xd6ad747a…2705

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…001f

0x1b6862…e19c

10 touches
10 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xce8bbe33…b72e

0x3bd359…433a

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

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 0xd6ad747aa3…df2705

← previous block·next block →recent activity