← previous blocknext block →recent activity

Analyzing

Block #73,651,810

20 transactions · 15 stateful · 2026-05-10 10:03:19 UTC

Parallelism

80/100

Blocked

40%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,651,810  ·  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

0xf2438038…5fa7

0x34b655…2a6f

6 touches
3 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x69bed3c2…6fd6

0x34b655…2a6f

4 touches
1 conflict

0xa2a9347c…3a0a

0x34b655…2a6f

4 touches
1 conflict

0xda68c75f…2912

0x34b655…2a6f

4 touches
1 conflict

0x38524fae…9deb

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0xf2438038b6…475fa7

← previous block·next block →recent activity