← previous blocknext block →recent activity

Analyzing

Block #72,310,217

9 transactions · 9 stateful · 2026-05-04 05:09:03 UTC

Parallelism

78/100

Blocked

22%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,310,217  ·  9 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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0008

0x5b7ec4…4016

4 touches
1 conflict

0x385a4934…210c

0x065c9d…c394

2 touches
0 conflicts

0x88a7f519…def5

0x065c9d…c394

2 touches
0 conflicts

0x729c91b8…953a

0x188d58…ea8e

2 touches
0 conflicts

0xac81b2fd…dfdd

0x188d58…ea8e

2 touches
0 conflicts

0xc041ec26…ae2c

0x188d58…ea8e

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: 0x34b6552d…112a6f

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity