Block #70,995,188

← previous blocknext block →recent activity

Analyzing

Block #70,995,188

10 transactions · 9 stateful · 2026-04-28 03:00:53 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,995,188  ·  10 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

0x75f2f0cd…a6df

0x065c9d…c394

4 touches
1 conflict

0x7c67a870…729b

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1c6f8b9b…8068

0x065c9d…c394

4 touches
1 conflict

0x2c9068fc…d345

0x065c9d…c394

4 touches
1 conflict

0x6364bde1…1038

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xcd621226…2df8

0x368ee5…7ca4

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 0x75f2f0cde2…3ca6df

← previous block·next block →recent activity