← previous blocknext block →recent activity

Analyzing

Block #72,233,750

29 transactions · 24 stateful · 2026-05-03 20:35:58 UTC

Parallelism

72/100

Blocked

46%

Avg conflicts / tx

1.28

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,233,750  ·  29 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0x1c389468…6b0e

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x388f889f…a655

0x34b655…2a6f

6 touches
3 conflicts

0x74e71984…ae90

0x2a68ba…90c5

4 touches
1 conflict

0x005fb969…2d97

0x34b655…2a6f

4 touches
1 conflict

0x17e2d2a0…359e

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity