← previous blocknext block →recent activity

Analyzing

Block #72,295,947

8 transactions · 6 stateful · 2026-05-04 03:33:57 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,295,947  ·  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

0x7566b4dc…e52a

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x92775b3a…8dc6

0x065c9d…c394

3 touches
1 conflict

0xdc30ea0c…a2ef

0x065c9d…c394

2 touches
0 conflicts

0xe0c616d2…4229

0x065c9d…c394

2 touches
0 conflicts

0x00000000…000b

0x8d0464…4402

2 touches
0 conflicts

0x0175b7a6…1db9

0x8d0464…4402

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 0x7566b4dc82…0de52a

← previous block·next block →recent activity