← previous blocknext block →recent activity

Analyzing

Block #73,048,453

14 transactions · 13 stateful · 2026-05-07 15:07:04 UTC

Parallelism

64/100

Blocked

46%

Avg conflicts / tx

1.07

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,048,453  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x7f189cf6…afab

0x065c9d…c394

6 touches
3 conflicts

0x92d6baf2…ee4c

0x065c9d…c394

4 touches
1 conflict

0x8e66da19…66b6

0x065c9d…c394

4 touches
1 conflict

0x2a354a63…0515

0x065c9d…c394

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0xccb24c49…7db0

0x065c9d…c394

3 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: 0x065c9d28…a9c394

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity