← previous blocknext block →recent activity

Analyzing

Block #72,399,164

14 transactions · 14 stateful · 2026-05-04 15:01:39 UTC

Parallelism

79/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,399,164  ·  14 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

0xd18a8dca…452b

0x1b6862…e19c

4 touches
1 conflict

0x2b9c6652…d14e

0x754704…b603

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xdd70bea3…1ffe

0x3bd359…433a

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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: 0x1b68626d…2de19c

1 conflict on slot 0xd18a8dca96…b8452b

← previous block·next block →recent activity