← previous blocknext block →recent activity

Analyzing

Block #72,497,892

16 transactions · 14 stateful · 2026-05-05 01:59:13 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,497,892  ·  16 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd2fb9655…0ed6

0x065c9d…c394

4 touches
1 conflict

0xfc26e40d…b28c

0x065c9d…c394

4 touches
1 conflict

0x7307ddc6…7fc5

0x065c9d…c394

3 touches
1 conflict

0x78ae8c48…a434

0x065c9d…c394

3 touches
1 conflict

0x49ca384c…e773

0x065c9d…c394

3 touches
1 conflict

0x5c8c6ab6…dc36

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 0x0000000000…00003d

← previous block·next block →recent activity