← previous blocknext block →recent activity

Analyzing

Block #72,097,971

25 transactions · 19 stateful · 2026-05-03 05:27:56 UTC

Parallelism

80/100

Blocked

53%

Avg conflicts / tx

0.88

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,097,971  ·  25 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

0x0d0b2509…074d

0x3bd359…433a

10 touches
10 conflicts

0xe6455d1f…1029

0x754704…b603

10 touches
10 conflicts

0x87dc7e24…e789

0xd32edf…ff58

9 touches
10 conflicts

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ad

0x8d66a4…3095

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0x46cb45de…a567

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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: 0x3bd359c1…15433a

10 conflicts on slot 0x0d0b2509ae…4b074d

← previous block·next block →recent activity