← previous blocknext block →recent activity

Analyzing

Block #73,921,098

12 transactions · 10 stateful · 2026-05-11 16:10:15 UTC

Parallelism

58/100

Blocked

60%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,921,098  ·  12 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

0xee230b20…5a0f

0x34b655…2a6f

8 touches
6 conflicts

0x96844849…b4b0

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf9ad4c21…c372

0xd32edf…ff58

5 touches
3 conflicts

0x9ac040c1…8220

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0000

0x249978…5353

4 touches
1 conflict

0x00000000…0001

0x249978…5353

4 touches
1 conflict

0x00000000…0003

0x249978…5353

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

6 conflicts on slot 0xee230b202a…c05a0f

← previous block·next block →recent activity