Block #73,210,727

← previous blocknext block →recent activity

Analyzing

Block #73,210,727

20 transactions · 19 stateful · 2026-05-08 09:06:43 UTC

Parallelism

70/100

Blocked

58%

Avg conflicts / tx

1.15

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,210,727  ·  20 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

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x66ce0d79…cbfe

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x94e0a693…b163

0x065c9d…c394

4 touches
2 conflicts

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0x200e1edd…bc96

0x065c9d…c394

4 touches
1 conflict

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

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity