← previous blocknext block →recent activity

Analyzing

Block #70,845,655

16 transactions · 13 stateful · 2026-04-27 10:24:58 UTC

Parallelism

75/100

Blocked

31%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,845,655  ·  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

0xd984a5e4…5cfc

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x53b4ef2b…8a05

0x34b655…2a6f

4 touches
1 conflict

0x820c9de7…b517

0x34b655…2a6f

4 touches
1 conflict

0xdf956ddc…e724

0x34b655…2a6f

4 touches
1 conflict

0xe2ffe0f7…de76

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

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: 0x34b6552d…112a6f

6 conflicts on slot 0xd984a5e4e9…3a5cfc

← previous block·next block →recent activity