← previous blocknext block →recent activity

Analyzing

Block #72,287,932

7 transactions · 6 stateful · 2026-05-04 02:40:09 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,287,932  ·  7 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

0x323e6a14…30e3

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x60b24061…7c23

0x188d58…ea8e

2 touches
0 conflicts

0x60b24061…7c25

0x188d58…ea8e

2 touches
0 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

2 touches
0 conflicts

0xe75ce681…ba60

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0013

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: 0x065c9d28…a9c394

3 conflicts on slot 0x323e6a141e…d530e3

← previous block·next block →recent activity