← previous blocknext block →recent activity

Analyzing

Block #70,846,516

16 transactions · 13 stateful · 2026-04-27 10:30:42 UTC

Parallelism

88/100

Blocked

15%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,846,516  ·  16 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

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x67eb012f…9549

0x065c9d…c394

4 touches
1 conflict

0x4d51f20a…d94b

0x065c9d…c394

3 touches
1 conflict

0x64c5b5e4…8058

0x065c9d…c394

3 touches
1 conflict

0x62e4cac3…0eeb

0x065c9d…c394

3 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: 0x2a68ba18…8e90c5

1 conflict on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity