← previous blocknext block →recent activity

Analyzing

Block #70,909,048

6 transactions · 6 stateful · 2026-04-27 17:27:10 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,909,048  ·  6 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

0x1c5ab28d…6221

0x065c9d…c394

3 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x245fd341…edd4

0x065c9d…c394

2 touches
0 conflicts

0x2a1abc7d…e07d

0x065c9d…c394

2 touches
0 conflicts

0xa08dd502…4da8

0x065c9d…c394

2 touches
0 conflicts

0xf53efa9d…588a

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 0x1c5ab28dbe…426221

← previous block·next block →recent activity