← previous blocknext block →recent activity

Analyzing

Block #70,998,363

6 transactions · 5 stateful · 2026-04-28 03:22:01 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,998,363  ·  6 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

0x2748d049…ccfd

0x065c9d…c394

4 touches
1 conflict

0x485e1f38…c6f3

0x065c9d…c394

4 touches
1 conflict

0x558f4da9…1005

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xbf46d9c4…5d62

0x065c9d…c394

4 touches
1 conflict

0xb8d2a209…558a

0x065c9d…c394

2 touches
1 conflict

0x01d5ec5f…365e

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 0x2748d049c2…57ccfd

← previous block·next block →recent activity