Block #70,951,813

← previous blocknext block →recent activity

Analyzing

Block #70,951,813

12 transactions · 10 stateful · 2026-04-27 22:11:52 UTC

Parallelism

83/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,951,813  ·  12 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

0x23d0d09a…183f

0x065c9d…c394

4 touches
1 conflict

0x789ef430…34e2

0x065c9d…c394

4 touches
1 conflict

0xc1f19aa0…1cd3

0x065c9d…c394

4 touches
1 conflict

0xfba24657…ee09

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

2 touches
0 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

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

1 conflict on slot 0x23d0d09aac…50183f

← previous block·next block →recent activity