← previous blocknext block →recent activity

Analyzing

Block #70,981,307

12 transactions · 11 stateful · 2026-04-28 01:28:25 UTC

Parallelism

67/100

Blocked

27%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,981,307  ·  12 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0xb138d087…4689

0x34b655…2a6f

4 touches
1 conflict

0x2af5f63a…b7b9

0x2e3234…7d90

2 touches
0 conflicts

0x241c0626…a1b8

0x73ada1…8be0

2 touches
0 conflicts

0x6149603d…cfa1

0x73ada1…8be0

2 touches
0 conflicts

0x8956cb26…42f7

0x73ada1…8be0

2 touches
0 conflicts

0x8956cb26…42fa

0x73ada1…8be0

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity