← previous blocknext block →recent activity

Analyzing

Block #72,209,715

5 transactions · 4 stateful · 2026-05-03 17:54:29 UTC

Parallelism

60/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,209,715  ·  5 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

0xcec8aa8d…ea1c

0x065c9d…c394

4 touches
1 conflict

0x4d61418f…1398

0x065c9d…c394

4 touches
1 conflict

0x7970413e…0e58

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x381464db…5989

0x065c9d…c394

3 touches
1 conflict

0xaa9fd95f…4bd2

0x065c9d…c394

3 touches
1 conflict

0x5bf4d882…102b

0x065c9d…c394

3 touches
1 conflict

0x5d17dcd3…71d2

0x065c9d…c394

3 touches
1 conflict

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 0xcec8aa8dd8…aaea1c

← previous block·next block →recent activity