← previous blocknext block →recent activity

Analyzing

Block #73,962,788

11 transactions · 8 stateful · 2026-05-11 20:47:33 UTC

Parallelism

64/100

Blocked

38%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,962,788  ·  11 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x54638670…c819

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x716f4c72…9116

0x065c9d…c394

2 touches
0 conflicts

0x84cb658b…4002

0x065c9d…c394

2 touches
0 conflicts

0x00000000…009a

0x16f70c…c3dd

2 touches
0 conflicts

0x72a152dd…9ff7

0x16f70c…c3dd

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity