← previous blocknext block →recent activity

Analyzing

Block #73,043,098

27 transactions · 23 stateful · 2026-05-07 14:31:22 UTC

Parallelism

78/100

Blocked

48%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,043,098  ·  27 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xce7bfe5e…5e58

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

6 touches
3 conflicts

0x20ac0567…c954

0x34b655…2a6f

6 touches
3 conflicts

0x2484cc15…5afc

0x34b655…2a6f

6 touches
3 conflicts

0x26bbcb47…263f

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 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: 0x065c9d28…a9c394

6 conflicts on slot 0xce7bfe5ef1…205e58

← previous block·next block →recent activity