← previous blocknext block →recent activity

Analyzing

Block #73,210,868

18 transactions · 15 stateful · 2026-05-08 09:07:39 UTC

Parallelism

83/100

Blocked

20%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,210,868  ·  18 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0x375b627a…a7e3

0x065c9d…c394

4 touches
1 conflict

0x18084d1a…ff39

0x065c9d…c394

3 touches
1 conflict

0x4dd1db39…a994

0x188d58…ea8e

2 touches
0 conflicts

0x4dd1db39…a996

0x188d58…ea8e

2 touches
0 conflicts

0xb1acfe51…c6b1

0x3bd359…433a

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