← previous blocknext block →recent activity

Analyzing

Block #73,683,655

13 transactions · 13 stateful · 2026-05-10 13:38:21 UTC

Parallelism

77/100

Blocked

31%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,683,655  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0x157b6348…8604

0x34b655…2a6f

2 touches
0 conflicts

0x207fb267…de78

0x34b655…2a6f

2 touches
0 conflicts

0x22863bf9…19df

0x34b655…2a6f

2 touches
0 conflicts

0x50c2960c…5f37

0x34b655…2a6f

2 touches
0 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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity