← previous blocknext block →recent activity

Analyzing

Block #73,653,912

56 transactions · 24 stateful · 2026-05-10 10:17:31 UTC

Parallelism

77/100

Blocked

67%

Avg conflicts / tx

1.46

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,653,912  ·  56 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x44f0095a…f680

0xd32edf…ff58

25 touches
78 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0xd91d51d6…d0ba

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0002

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

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: 0xd32edf66…9fff58

78 conflicts on slot 0x44f0095aa6…87f680

← previous block·next block →recent activity