← previous blocknext block →recent activity

Analyzing

Block #73,809,443

9 transactions · 7 stateful · 2026-05-11 03:46:31 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,809,443  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0x6f66a11b…0ed4

0x065c9d…c394

2 touches
0 conflicts

0xa16ba27b…0edd

0x065c9d…c394

2 touches
0 conflicts

0x01ee9594…4861

0x0cb7d2…2db7

2 touches
0 conflicts

0x63f9e7c8…c42d

0x23c26b…7777

2 touches
0 conflicts

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

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity