← previous blocknext block →recent activity

Analyzing

Block #72,267,257

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

Parallelism

88/100

Blocked

25%

Avg conflicts / tx

0.12

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,267,257  ·  17 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

0xda8ee426…738c

0x065c9d…c394

4 touches
1 conflict

0x74a63b2b…d9f3

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0x7e9d3a…9fda

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x3007f337…a0a1

0x065c9d…c394

3 touches
1 conflict

0xa5867c2e…64f5

0x065c9d…c394

3 touches
1 conflict

0x86f469ab…a0b3

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

1 conflict on slot 0xda8ee426f7…82738c

← previous block·next block →recent activity