Block #72,214,308

← previous blocknext block →recent activity

Analyzing

Block #72,214,308

7 transactions · 7 stateful · 2026-05-03 18:25:23 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,214,308  ·  7 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

0x083ad6a1…6b04

0x065c9d…c394

2 touches
0 conflicts

0x34b75579…8e4c

0x065c9d…c394

2 touches
0 conflicts

0x7542e761…f45b

0x065c9d…c394

2 touches
0 conflicts

0x84478b8d…a4c2

0x065c9d…c394

2 touches
0 conflicts

0xb3022d4c…8d1b

0x065c9d…c394

2 touches
0 conflicts

0xd221d591…95b8

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