Block #70,996,225

← previous blocknext block →recent activity

Analyzing

Block #70,996,225

9 transactions · 9 stateful · 2026-04-28 03:07:47 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,996,225  ·  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

0x35d9a523…b36b

0x065c9d…c394

4 touches
1 conflict

0x5cb735e4…8ff5

0x065c9d…c394

4 touches
1 conflict

0x620e09b3…7cd5

0x065c9d…c394

4 touches
1 conflict

0x7c083258…4533

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x15bae5fc…9f7e

0x57ea24…2cec

2 touches
0 conflicts

0xa110274b…1790

0x57ea24…2cec

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 0x35d9a523f5…48b36b

← previous block·next block →recent activity