← previous blocknext block →recent activity

Analyzing

Block #72,496,440

7 transactions · 7 stateful · 2026-05-05 01:49:34 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x394c3833…b4ab

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x9783ac30…7b37

0x065c9d…c394

3 touches
1 conflict

0x79219563…0b74

0xd32edf…ff58

3 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x8876d94c…8435

0x2a68ba…90c5

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

1 conflict on slot 0x0000000000…000013

← previous block·next block →recent activity