← previous blocknext block →recent activity

Analyzing

Block #70,891,603

19 transactions · 13 stateful · 2026-04-27 15:30:58 UTC

Parallelism

63/100

Blocked

46%

Avg conflicts / tx

0.74

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,891,603  ·  19 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

0xc3c8642a…7da5

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x4c157bff…3936

0xd32edf…ff58

5 touches
3 conflicts

0xefda5795…7082

0x065c9d…c394

5 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0xcb45d9d6…cb84

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

10 conflicts on slot 0xc3c8642ae9…317da5

← previous block·next block →recent activity