Block #72,213,393

← previous blocknext block →recent activity

Analyzing

Block #72,213,393

14 transactions · 11 stateful · 2026-05-03 18:19:14 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,213,393  ·  14 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

0xbf04f37d…85f2

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x47bf9ae7…17c4

0x065c9d…c394

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7ec5e2bb…c35c

0x065c9d…c394

4 touches
1 conflict

0xcf93e3d0…9fbf

0x065c9d…c394

3 touches
1 conflict

0x3cb05d9d…68f9

0x065c9d…c394

3 touches
1 conflict

0x00000000…0004

0x094452…0a09

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

6 conflicts on slot 0xbf04f37d93…8a85f2

← previous block·next block →recent activity