← previous blocknext block →recent activity

Analyzing

Block #72,978,128

21 transactions · 17 stateful · 2026-05-07 07:18:58 UTC

Parallelism

86/100

Blocked

47%

Avg conflicts / tx

0.52

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,978,128  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xd8343857…b9a7

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0004

0xd5b70d…615b

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity