← previous blocknext block →recent activity

Analyzing

Block #73,661,317

20 transactions · 18 stateful · 2026-05-10 11:07:23 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,661,317  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0d0b2509…074d

0x3bd359…433a

8 touches
6 conflicts

0xe6455d1f…1029

0x754704…b603

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x885efce3…7496

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: 0x3bd359c1…15433a

6 conflicts on slot 0x0d0b2509ae…4b074d

← previous block·next block →recent activity