← previous blocknext block →recent activity

Analyzing

Block #72,497,107

14 transactions · 14 stateful · 2026-05-05 01:54:00 UTC

Parallelism

86/100

Blocked

7%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,497,107  ·  14 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xca04c7ad…7612

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0x7e9d3a…9fda

2 touches
0 conflicts

0x00bac013…a28c

0x91b81b…6d56

2 touches
0 conflicts

0x9560013d…8caf

0x91b81b…6d56

2 touches
0 conflicts

0x2b861c51…32bb

0xd42a27…01c7

2 touches
0 conflicts

0x455b104f…3960

0xea1b8e…c5ec

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity