← previous blocknext block →recent activity

Analyzing

Block #72,496,373

10 transactions · 10 stateful · 2026-05-05 01:49:07 UTC

Parallelism

70/100

Blocked

30%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,496,373  ·  10 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

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x0acb2c12…cb0a

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xef9cf7b0…46d7

0x065c9d…c394

3 touches
1 conflict

0x0d57da06…62cb

0x065c9d…c394

2 touches
0 conflicts

0x1d16b951…b08f

0x065c9d…c394

2 touches
0 conflicts

0x33b19b24…0b55

0x065c9d…c394

2 touches
0 conflicts

0x3cd91bc3…061f

0x065c9d…c394

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: 0x681e908b…e1ae09

3 conflicts on slot 0x0d622e34f9…000000

← previous block·next block →recent activity