← previous blocknext block →recent activity

Analyzing

Block #70,982,145

9 transactions · 7 stateful · 2026-04-28 01:34:00 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,982,145  ·  9 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

0xb6b74ae0…8d5e

0xea1b8e…c5ec

4 touches
1 conflict

0xc2fc05e8…5252

0xea1b8e…c5ec

4 touches
1 conflict

0xd8eb2d31…2ac0

0xea1b8e…c5ec

4 touches
1 conflict

0xfecd05e7…296f

0xea1b8e…c5ec

4 touches
1 conflict

0xfecd05e7…2970

0xea1b8e…c5ec

4 touches
1 conflict

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x9560013d…8caf

0xfd44b3…00d1

4 touches
1 conflict

0xb309ae5d…0ce7

0x2a68ba…90c5

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: 0xea1b8e4a…8fc5ec

1 conflict on slot 0xb6b74ae0ff…d48d5e

← previous block·next block →recent activity