← previous blocknext block →recent activity

Analyzing

Block #73,911,890

20 transactions · 20 stateful · 2026-05-11 15:08:49 UTC

Parallelism

40/100

Blocked

70%

Avg conflicts / tx

3.6

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,911,890  ·  20 txs across 12 waves  ·  depth 12
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

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

0xed385e36…0251

0x7b2728…7777

24 touches
66 conflicts

0x00000000…0000

0x3e1523…94aa

24 touches
66 conflicts

0x00000000…0002

0x3e1523…94aa

24 touches
66 conflicts

0x00000000…0003

0x3e1523…94aa

24 touches
66 conflicts

0xe4b00f4b…34c0

0x3bd359…433a

24 touches
66 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x9937bf52…9371

0x065c9d…c394

4 touches
1 conflict

0x39678648…6205

0x065c9d…c394

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: 0x7b2728c0…a97777

66 conflicts on slot 0xed385e3655…300251

← previous block·next block →recent activity