Block #70,995,180

← previous blocknext block →recent activity

Analyzing

Block #70,995,180

18 transactions · 12 stateful · 2026-04-28 03:00:50 UTC

Parallelism

61/100

Blocked

67%

Avg conflicts / tx

1.44

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,995,180  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x45bdadd2…0df3

0xd32edf…ff58

13 touches
21 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0xc29f4ca0…8c7f

0x065c9d…c394

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

4 touches
1 conflict

0x35801c67…bcc4

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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: 0xd32edf66…9fff58

21 conflicts on slot 0x45bdadd24d…fb0df3

← previous block·next block →recent activity