← previous blocknext block →recent activity

Analyzing

Block #70,891,589

13 transactions · 12 stateful · 2026-04-27 15:30:53 UTC

Parallelism

77/100

Blocked

17%

Avg conflicts / tx

0.15

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,891,589  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x6ea8fa8d…3dd8

0x1b6862…e19c

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x81d39866…42f6

0x065c9d…c394

3 touches
1 conflict

0xfaad1f25…fe1b

0xd32edf…ff58

3 touches
1 conflict

0x807e1273…3c99

0x3bd359…433a

2 touches
0 conflicts

0xcce2fd99…a8eb

0x3bd359…433a

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: 0x1b68626d…2de19c

1 conflict on slot 0x0000000000…000013

← previous block·next block →recent activity