← previous blocknext block →recent activity

Analyzing

Block #73,176,533

19 transactions · 16 stateful · 2026-05-08 05:19:01 UTC

Parallelism

84/100

Blocked

19%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,176,533  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x2a354a63…0515

0x065c9d…c394

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

2 touches
0 conflicts

0x1c68a347…408e

0x34b655…2a6f

2 touches
0 conflicts

0x21d22421…0b7a

0x34b655…2a6f

2 touches
0 conflicts

0x251861eb…78fd

0x34b655…2a6f

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity