Block #73,211,803

← previous blocknext block →recent activity

Analyzing

Block #73,211,803

9 transactions · 6 stateful · 2026-05-08 09:13:50 UTC

Parallelism

78/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,211,803  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xce7bfe5e…5e58

0x065c9d…c394

4 touches
1 conflict

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x51087f5a…61f7

0x34b655…2a6f

2 touches
0 conflicts

0xa9988419…9f45

0x34b655…2a6f

2 touches
0 conflicts

0x17cd1479…00bb

0x8d66a4…3095

2 touches
0 conflicts

0x7f430e47…4cbd

0x8d66a4…3095

2 touches
0 conflicts

0x8a35acfb…d1a8

0x8d66a4…3095

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

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity