Block #70,908,874

← previous blocknext block →recent activity

Analyzing

Block #70,908,874

10 transactions · 9 stateful · 2026-04-27 17:26:00 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,908,874  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x1b9e654e…0a08

0x34b655…2a6f

4 touches
1 conflict

0x23951077…539b

0x34b655…2a6f

4 touches
1 conflict

0x313f2565…5b00

0x34b655…2a6f

4 touches
1 conflict

0x3ac9e0f2…b632

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

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: 0xc8689a47…62ee79

1 conflict on slot 0xc6417de023…802191

← previous block·next block →recent activity