← previous blocknext block →recent activity

Analyzing

Block #70,918,208

23 transactions · 20 stateful · 2026-04-27 18:28:13 UTC

Parallelism

87/100

Blocked

25%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,918,208  ·  23 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x489cb750…7069

0x131a2e…0da9

4 touches
1 conflict

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0x24968e6d…0132

0x131a2e…0da9

4 touches
1 conflict

0x8fb6c28d…8890

0xd32edf…ff58

3 touches
1 conflict

0xba5743c7…21c4

0x1b6862…e19c

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity