Block #70,986,540

← previous blocknext block →recent activity

Analyzing

Block #70,986,540

22 transactions · 22 stateful · 2026-04-28 02:03:16 UTC

Parallelism

68/100

Blocked

45%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,986,540  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x9e0e23b5…6910

0x34b655…2a6f

6 touches
3 conflicts

0x445b51c5…0be4

0x34b655…2a6f

6 touches
3 conflicts

0x75f6889e…7f1e

0x34b655…2a6f

6 touches
3 conflicts

0xb0d07380…8405

0x065c9d…c394

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba60

0x188d58…ea8e

4 touches
1 conflict

0x0cb5b886…beee

0x34b655…2a6f

4 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: 0x34b6552d…112a6f

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity