← previous blocknext block →recent activity

Analyzing

Block #72,272,298

10 transactions · 8 stateful · 2026-05-04 00:55:00 UTC

Parallelism

70/100

Blocked

25%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,272,298  ·  10 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…003d

0x065c9d…c394

6 touches
3 conflicts

0x3dd5ddc2…26e5

0x065c9d…c394

4 touches
1 conflict

0xb9855a25…eecd

0x065c9d…c394

3 touches
1 conflict

0x379cf9a8…f0fa

0x065c9d…c394

2 touches
0 conflicts

0x74a63b2b…d9f3

0x065c9d…c394

2 touches
0 conflicts

0x792d3f3e…d724

0x065c9d…c394

2 touches
0 conflicts

0x8577229b…bbb7

0x065c9d…c394

2 touches
0 conflicts

0xabe44c5a…1d8e

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity