← previous blocknext block →recent activity

Analyzing

Block #73,043,214

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

Parallelism

79/100

Blocked

50%

Avg conflicts / tx

0.62

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,043,214  ·  29 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

10 touches
10 conflicts

0x251861eb…78fd

0x34b655…2a6f

8 touches
6 conflicts

0x16d7afd2…261b

0x34b655…2a6f

6 touches
3 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x1e64afb5…d536

0x34b655…2a6f

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

6 touches
3 conflicts

0x3702b140…97ea

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

10 conflicts on slot 0xce7bfe5ef1…205e58

← previous block·next block →recent activity