← previous blocknext block →recent activity

Analyzing

Block #72,430,962

9 transactions · 8 stateful · 2026-05-04 18:33:29 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,430,962  ·  9 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

0x641245e3…6323

0xc8689a…ee79

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0c7ac0ef…cdd2

0x065c9d…c394

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xfccb5285…cae7

0x065c9d…c394

3 touches
1 conflict

0x4c593fcb…1005

0x065c9d…c394

3 touches
1 conflict

0xbfe137fa…5fa8

0x065c9d…c394

3 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: 0xc8689a47…62ee79

1 conflict on slot 0x641245e3bc…1b6323

← previous block·next block →recent activity