Block #72,296,547

← previous blocknext block →recent activity

Analyzing

Block #72,296,547

8 transactions · 5 stateful · 2026-05-04 03:37:57 UTC

Parallelism

75/100

Blocked

20%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,296,547  ·  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

0x5c2aede2…3e1d

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2213b88b…dea3

0x065c9d…c394

3 touches
1 conflict

0x85827d9c…173e

0x065c9d…c394

3 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x47f3e199…cbc8

0x065c9d…c394

2 touches
0 conflicts

0x8437e96b…fe65

0x065c9d…c394

2 touches
0 conflicts

0xb182240d…dfb4

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 0x5c2aede2f5…dc3e1d

← previous block·next block →recent activity