← previous blocknext block →recent activity

Analyzing

Block #70,982,160

9 transactions · 8 stateful · 2026-04-28 01:34:06 UTC

Parallelism

78/100

Blocked

25%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,982,160  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xbfca3cd0…5023

0x34b655…2a6f

4 touches
1 conflict

0x5f6ba77d…a4b8

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x4546ebad…b908

0x34b655…2a6f

2 touches
0 conflicts

0x68b53e57…0091

0x34b655…2a6f

2 touches
0 conflicts

0x84fb2a36…db89

0x34b655…2a6f

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

1 conflict on slot 0xbfca3cd067…cd5023

← previous block·next block →recent activity