← previous blocknext block →recent activity

Analyzing

Block #73,682,815

20 transactions · 16 stateful · 2026-05-10 13:32:39 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,682,815  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x3e733ae4…4598

0x34b655…2a6f

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0xed57bddf…1abf

0xc8689a…ee79

4 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0xc5564f8e…f4bf

0x6c4bfa…a540

4 touches
1 conflict

0xf0f673fd…37a7

0x6c4bfa…a540

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity