← previous blocknext block →recent activity

Analyzing

Block #73,200,227

15 transactions · 14 stateful · 2026-05-08 07:56:53 UTC

Parallelism

67/100

Blocked

36%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,200,227  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8e66da19…66b6

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x2a354a63…0515

0x065c9d…c394

4 touches
1 conflict

0x3e5a01f6…d869

0x065c9d…c394

4 touches
1 conflict

0xcd18274a…cefb

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4de57e01…aab9

0x065c9d…c394

3 touches
1 conflict

0xce71eb25…aafa

0x065c9d…c394

3 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: 0x065c9d28…a9c394

6 conflicts on slot 0x8e66da1932…c966b6

← previous block·next block →recent activity