← previous blocknext block →recent activity

Analyzing

Block #72,365,696

8 transactions · 7 stateful · 2026-05-04 11:18:35 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,365,696  ·  8 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

0x71f22d99…e4cd

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xacd76ffc…a846

0x065c9d…c394

3 touches
1 conflict

0x00000000…0004

0x026864…26e6

2 touches
0 conflicts

0x7085488e…4b60

0x065c9d…c394

2 touches
0 conflicts

0x86b4f3b9…2008

0x065c9d…c394

2 touches
0 conflicts

0x9884184f…3be2

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

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 0x71f22d99ce…62e4cd

← previous block·next block →recent activity