← previous blocknext block →recent activity

Analyzing

Block #70,957,042

15 transactions · 14 stateful · 2026-04-27 22:46:40 UTC

Parallelism

73/100

Blocked

29%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,957,042  ·  15 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

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x0dbf9688…c6cf

0xd18b7e…414b

4 touches
1 conflict

0x8242e39e…65a0

0x065c9d…c394

3 touches
1 conflict

0xdb34a824…c05d

0xd32edf…ff58

3 touches
1 conflict

0xe2d92952…4e1f

0x065c9d…c394

3 touches
1 conflict

0xf8127de7…d5ec

0x3bd359…433a

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

6 conflicts on slot 0xc3c8642ae9…317da5

← previous block·next block →recent activity