Block #70,995,113

← previous blocknext block →recent activity

Analyzing

Block #70,995,113

10 transactions · 8 stateful · 2026-04-28 03:00:23 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x86a4ccf3…7288

0x065c9d…c394

4 touches
1 conflict

0xadd35f0c…eca9

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xb5ee107f…a6e6

0x065c9d…c394

4 touches
1 conflict

0x4ddb2e3d…1132

0x065c9d…c394

2 touches
1 conflict

0x4ddb2e3d…1133

0x065c9d…c394

2 touches
1 conflict

0x9c797528…9e8d

0x065c9d…c394

2 touches
1 conflict

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 0x0000000000…00003d

← previous block·next block →recent activity