Block #72,371,101

← previous blocknext block →recent activity

Analyzing

Block #72,371,101

14 transactions · 12 stateful · 2026-05-04 11:54:33 UTC

Parallelism

57/100

Blocked

42%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,371,101  ·  14 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x1c913164…5c2e

0x34b655…2a6f

8 touches
6 conflicts

0x50059a18…9b7b

0x34b655…2a6f

6 touches
3 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0x9948dde8…6a26

0x34b655…2a6f

4 touches
1 conflict

0xac8e97a0…8426

0x34b655…2a6f

4 touches
1 conflict

0x0335ae80…8414

0x8d66a4…3095

4 touches
1 conflict

0x17cd1479…00bb

0x8d66a4…3095

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity