← previous blocknext block →recent activity

Analyzing

Block #70,909,198

16 transactions · 16 stateful · 2026-04-27 17:28:10 UTC

Parallelism

75/100

Blocked

25%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,909,198  ·  16 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

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0x892565c7…29cd

0x065c9d…c394

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a568

0x188d58…ea8e

4 touches
1 conflict

0x60b24061…7c23

0x188d58…ea8e

4 touches
1 conflict

0x60b24061…7c25

0x188d58…ea8e

4 touches
1 conflict

0x9413ddeb…70dd

0x188d58…ea8e

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xc3c8642ae9…317da5

← previous block·next block →recent activity