← previous blocknext block →recent activity

Analyzing

Block #70,862,095

8 transactions · 8 stateful · 2026-04-27 12:14:30 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,862,095  ·  8 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

0x420b6c36…34d8

0x065c9d…c394

4 touches
1 conflict

0x54d1d767…97f0

0x065c9d…c394

4 touches
1 conflict

0x78ecc48f…8546

0x065c9d…c394

4 touches
1 conflict

0xa096e8f9…53ce

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x00000000…0006

0x60bb42…87ea

2 touches
0 conflicts

0x4039b31f…0f4a

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 0x420b6c3670…e434d8

← previous block·next block →recent activity