Block #70,918,188

← previous blocknext block →recent activity

Analyzing

Block #70,918,188

26 transactions · 25 stateful · 2026-04-27 18:28:05 UTC

Parallelism

73/100

Blocked

60%

Avg conflicts / tx

1.73

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,918,188  ·  26 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

0x3ea1512f…5939

0xd32edf…ff58

13 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

8 touches
6 conflicts

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

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 0x3ea1512f13…9b5939

← previous block·next block →recent activity