Block #72,976,109

← previous blocknext block →recent activity

Analyzing

Block #72,976,109

11 transactions · 8 stateful · 2026-05-07 07:05:30 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,976,109  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0xdaca243a…f9de

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0x476f6acc…b194

0x065c9d…c394

2 touches
0 conflicts

0x8b15a642…b763

0x065c9d…c394

2 touches
0 conflicts

0x99280570…f4bd

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: 0x34b6552d…112a6f

1 conflict on slot 0x1b5d2e607a…9999b5

← previous block·next block →recent activity