← previous blocknext block →recent activity

Analyzing

Block #72,233,841

33 transactions · 25 stateful · 2026-05-03 20:36:35 UTC

Parallelism

88/100

Blocked

40%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,233,841  ·  33 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0x5a2eb64f…5647

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0002

0x7e9d3a…9fda

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x8a032547…e2cd

0x065c9d…c394

5 touches
3 conflicts

0x873f3074…b830

0xee8c0e…1242

4 touches
1 conflict

0x08b8e539…b9f9

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

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: 0x681e908b…e1ae09

6 conflicts on slot 0x0d622e34f9…000000

← previous block·next block →recent activity