← previous blocknext block →recent activity

Analyzing

Block #70,994,924

18 transactions · 16 stateful · 2026-04-28 02:59:07 UTC

Parallelism

72/100

Blocked

31%

Avg conflicts / tx

0.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,994,924  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x3b3a5945…10d0

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc03a03cd…fbcf

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0x1c913164…5c2e

0x34b655…2a6f

4 touches
1 conflict

0x1d003c7b…b055

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

3 conflicts on slot 0x3b3a5945a9…c610d0

← previous block·next block →recent activity