Block #70,862,855

← previous blocknext block →recent activity

Analyzing

Block #70,862,855

16 transactions · 14 stateful · 2026-04-27 12:19:33 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,862,855  ·  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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0xd8786952…a0d0

0x065c9d…c394

2 touches
0 conflicts

0xf0b9fb34…c044

0x065c9d…c394

2 touches
0 conflicts

0x2a354a63…0515

0x131a2e…0da9

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity