← previous blocknext block →recent activity

Analyzing

Block #70,909,196

18 transactions · 15 stateful · 2026-04-27 17:28:09 UTC

Parallelism

83/100

Blocked

40%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,909,196  ·  18 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…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x46e9c4e5…5292

0x065c9d…c394

4 touches
1 conflict

0x797e3f4a…c3f0

0x065c9d…c394

4 touches
1 conflict

0xda0a2ab6…fd3a

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x35323df1…7129

0x065c9d…c394

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: 0xd0f8a642…83badc

3 conflicts on slot 0x0000000000…000004

← previous block·next block →recent activity