← previous blocknext block →recent activity

Analyzing

Block #70,891,588

25 transactions · 18 stateful · 2026-04-27 15:30:52 UTC

Parallelism

84/100

Blocked

28%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,891,588  ·  25 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

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x371ff2b0…80b9

0x065c9d…c394

6 touches
3 conflicts

0x6ca355be…9d4b

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0001

0x2b37ef…0bdc

2 touches
0 conflicts

0x00000000…000c

0x2b37ef…0bdc

2 touches
0 conflicts

0x00000000…000d

0x2b37ef…0bdc

2 touches
0 conflicts

0x00000000…000e

0x2b37ef…0bdc

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

6 conflicts on slot 0xc3c8642ae9…317da5

← previous block·next block →recent activity