← previous blocknext block →recent activity

Analyzing

Block #70,878,376

32 transactions · 27 stateful · 2026-04-27 14:02:57 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,878,376  ·  32 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…0002

0xb857c1…9be1

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x41335ddf…94b9

0x34b655…2a6f

6 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x0a809ce1…7894

0x34b655…2a6f

4 touches
1 conflict

0x8d0e98f3…7ba0

0x34b655…2a6f

4 touches
1 conflict

0xb77c59ad…4c74

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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: 0xb857c13a…1a9be1

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity