← previous blocknext block →recent activity

Analyzing

Block #70,955,804

8 transactions · 7 stateful · 2026-04-27 22:38:26 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,955,804  ·  8 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…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x2d487a0a…89b8

0x065c9d…c394

2 touches
0 conflicts

0x382f3a72…a324

0x065c9d…c394

2 touches
0 conflicts

0x3da11c10…aa48

0x065c9d…c394

2 touches
0 conflicts

0x6a08f30b…402a

0x065c9d…c394

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity