← previous blocknext block →recent activity

Analyzing

Block #72,976,312

16 transactions · 12 stateful · 2026-05-07 07:06:52 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,976,312  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xca31fa68…1162

0xd32edf…ff58

5 touches
3 conflicts

0x4e5ebbf7…ae70

0xc8689a…ee79

4 touches
1 conflict

0xc5564f8e…f4bf

0x6ca43f…c331

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x1a4b4152…0a08

0x6ca43f…c331

4 touches
1 conflict

0xf0f673fd…37a7

0x6ca43f…c331

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x6ca43f…c331

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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: 0xd32edf66…9fff58

3 conflicts on slot 0xca31fa68e0…9a1162

← previous block·next block →recent activity