← previous blocknext block →recent activity

Analyzing

Block #73,918,871

25 transactions · 22 stateful · 2026-05-11 15:55:27 UTC

Parallelism

72/100

Blocked

59%

Avg conflicts / tx

1.36

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,918,871  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x757254ae…d917

0x34b655…2a6f

6 touches
3 conflicts

0xa15427f6…d932

0x34b655…2a6f

6 touches
3 conflicts

0x4b268018…02fb

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity