← previous blocknext block →recent activity

Analyzing

Block #70,845,727

13 transactions · 10 stateful · 2026-04-27 10:25:27 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,845,727  ·  13 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

0x2fd406b4…07fc

0x065c9d…c394

4 touches
1 conflict

0x345d4cc8…8ff4

0x065c9d…c394

4 touches
1 conflict

0xb7bc1a95…446c

0x065c9d…c394

4 touches
1 conflict

0xf013b2fd…4946

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

2 touches
0 conflicts

0x27007746…0502

0x754704…b603

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 0x2fd406b487…7707fc

← previous block·next block →recent activity