← previous blocknext block →recent activity

Analyzing

Block #72,366,301

8 transactions · 8 stateful · 2026-05-04 11:22:36 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,366,301  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x283a9549…68d7

0x065c9d…c394

2 touches
0 conflicts

0x42a58754…1d25

0x065c9d…c394

2 touches
0 conflicts

0xb0ad2353…3356

0x065c9d…c394

2 touches
0 conflicts

0xbde75edb…f4ba

0x065c9d…c394

2 touches
0 conflicts

0xefeb7f04…5473

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