← previous blocknext block →recent activity

Analyzing

Block #73,808,551

15 transactions · 14 stateful · 2026-05-11 03:40:33 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,808,551  ·  15 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

0x8240d70c…7c3b

0x34b655…2a6f

6 touches
3 conflicts

0x9b675023…d916

0x065c9d…c394

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x23114fac…630a

0x34b655…2a6f

4 touches
1 conflict

0x3d93727e…c307

0x34b655…2a6f

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

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

3 conflicts on slot 0x8240d70c8a…f27c3b

← previous block·next block →recent activity