← previous blocknext block →recent activity

Analyzing

Block #72,977,397

6 transactions · 5 stateful · 2026-05-07 07:14:06 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,977,397  ·  6 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

0xfa1891ba…0dc5

0x065c9d…c394

4 touches
1 conflict

0x022d153e…660b

0x065c9d…c394

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x001008bf…a75c

0x065c9d…c394

3 touches
1 conflict

0x8f074a09…b891

0x065c9d…c394

3 touches
1 conflict

0x93ca200c…0cd7

0x065c9d…c394

3 touches
1 conflict

0xcc1c139e…6b40

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: 0x065c9d28…a9c394

1 conflict on slot 0xfa1891ba36…030dc5

← previous block·next block →recent activity