← previous blocknext block →recent activity

Analyzing

Block #70,999,145

15 transactions · 13 stateful · 2026-04-28 03:27:09 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,999,145  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x35d9a523…b36b

0x065c9d…c394

5 touches
3 conflicts

0x432bfdd0…4ca0

0x065c9d…c394

5 touches
3 conflicts

0x7e709c41…b0df

0x065c9d…c394

5 touches
3 conflicts

0x15e69e02…5b53

0x065c9d…c394

5 touches
3 conflicts

0x462c8be7…4f83

0x8d66a4…3095

4 touches
1 conflict

0x468c69b1…af11

0x8d66a4…3095

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity