Block #70,862,479

← previous blocknext block →recent activity

Analyzing

Block #70,862,479

16 transactions · 13 stateful · 2026-04-27 12:17:04 UTC

Parallelism

75/100

Blocked

38%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,862,479  ·  16 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

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a568

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xda6b535e…6d6b

0x1b6862…e19c

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x0dbf9688…c6cf

0xd18b7e…414b

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: 0x188d586d…f9ea8e

1 conflict on slot 0x46cb45de01…66a566

← previous block·next block →recent activity